Closed KedoKudo closed 5 years ago
@KedoKudo Thank you for the suggestions. Could you please elaborate on your benchmark comment? Do you mean benchmarking the particle packing simulation time?
As a user, I would prefer to know what is the most time consuming aspect of kanapy
and the corresponding scalability (lognorm, linear, quadratic, etc.). I can use these information to extrapolate a rough estimate of the total computational time required for my workflow. For example, if I am using kanapy
to generate the microstructure input for my micromechanics simulation, I need to decide whether I want to bundle the two steps into one HPCC job. If generating a microstructure only accounts for a fraction of the total simulation time and it scales very well, I would probably bundle two steps into one and use the total simulation time as a rough estimate to request time on HPCC. Otherwise, I would most likely submit separate requests to maximize my chance of getting the time.
@KedoKudo Based on you suggestions for documentation improvement, I have updated the following:
The contents of the .dump file has been described in the Usage section under the heading: Visualize the packing simulation.
The user can now specify in the input file, the output unit in which the ABAQUS file and the Output statistics can be exported.
In the documentation, under the section Applications, I have added a sub-section called Simulation benchmarks. This details the CPU time required for particle packing and voxelization routines. These are the critical aspects of Kanapy.
src.kanapy. has been changed to kanapy. in the documentation.
@mrgprasad Thank you for adding the benchmark and various other edits in the documentation. I will close this issue now.
@mrgprasad Currently
kanapy
has a very extensive documentation, but I think most users could appreciate if the following aspects of the documentation can be improved:kanapy
src.kanapy.*
tokanapy.*
in the documentation