All previous questions solved.
Still waiting for one last zoom test (moderate resolution 512^3) to compare it with
gadget results but full box and low res zoom look ok.
We should start thinking in the baryon format output.
Here I write a list of to-do things:
- Find a clever way to set the char array in header. Should be set in the config file and then probably use some getValue?
- Re-check velocity units
- How important is the EKIN parameter of the header to start ART. We are not calculating it. It could be done when writing the files but seems to much work taking into account that it is probably calculated at each timestep.
- astep parameter: clarification on how is set/chosen for the initial conditions. It is important for subsequent steps or ART auto-regulates the next steps?
- Need some clarifications for zoom-in simulations:
+ which NROWC and NGRIDC is used (now using levelmin, but levelmax?)
+ Number of files. Not clear if all together in one or one for each level (in the last case we will need to do some important changes in the module)
- Confirm our current format is standard for all ART versions.
also the 'LINGER++' one was present (they used the same class name, so which one
was actually used depended on the compile order rather than the user choice).
