Best Of

Hi Philip, have you ever heard of any CRO company that uses SLC to write reports and passes the FDA review? Also, I heard that CDISC has standards for statistical software. Does this have any impact?

Best Regards.

I am not aware of any CROs that are currently using Altair SLC, but @Nico Chart may be able to report if there are any, without revealing their names.

I am currently writing a book about SAS programming, which includes chapters about the Altair Analytics Workbench. One chapter looks at whether Altair SLC could be used with clinical trials data processing. I have included some extracts below:

I hope this is helpful............Phil

Akash Purushothaman,

converting from an explicit solver to an implicit solver can be tricky, as in many cases we will focus on elastic material behavior in  implicit computations. Also, the way non-linearity is defined from one solver to another may vary (eg one solver can request a stress vs plastic strain curve, whereas the other looks for stress vs total strain).

So for materials it is not straightforward to get the proper conversion.

For such case, the best approach is still to look at both solver documentations, to check how to adopt the parameters, and ideally to run some sample tests with both solvers to check if you get the same behavior.

Once this done, you can populate your own material database and call the appropriate material card, depending on your solver.

Coming back to the Radioss to Abaqus conversion, this is indeed one of the conversion we do not support from the drop-down menu Tools -> Convert.That said, from 2021, we have improved the type of entities that can be converted just by switching the user profile. You should at least get elements, nodes, properties, sets get converted with version 2021. Please note that for conversion, we improve regularly the capabilities so do not hesitate to test more recent versions. Conversion still won't be exhaustive, but we may have increased our coverage.

Best Regards,

Michael

hi Qi,

On GPU the function is split into 3 parts, particle, simulation and geometry are in the 3 different functions.  On CPU it's all 1 function.

You should be able to find the documentation in the API Help 

C:\Program Files\Altair\2023\EDEM\src\Api\Help > Index.html

On CUDA GPU:

1. configForTimeStepParticleProperty. This will be run once for every particle once every timestep, before any contacts are computed. This is available for all 3 types of plugin shown above and an empty implementation must be provided if it is not required.
2. configForTimeStepTriangleProperty. This will be run once for every triangle once every timestep before any contacts are computed. This is only applicable for particle-geometry contact models (2 above) and an empty implementation must be provided in the GPU file if it is not required.
3. configForTimeStepSimulationProperty. This will be run once per timestep before any contacts are computed. This is available for all 3 types of plugin shown above and an empty implementation must be provided if it is not required. Note that this function is not available on the OpenCL solver.

On CPU:

Enables custom functionality to be carried out on a per timestep basis.