-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recreating a MUSIC zoom within genetIC #68
Comments
Sadly it's not quite that simple, because MUSIC uses a different (real space) approach to combining different levels. So, one can only really import level 0 in this sense. A tool to import MUSIC grids would certainly be useful, but it would need a bit more work; I imagine it essentially boils down to implementing a version of the |
Ah I see, thanks for the clarification! To be clear, with the current implementation, the But since genetIC implements zooms in a novel approach, we cannot reproduce zoom initial conditions from other IC codes (GRAFIC2, MUSIC or tipsy zooms) without significant implementations of method interfaces? Martin |
Yes that’s correct!
|
Ok! I don't have plans or time to implement such MUSIC interface soon, so I can either close this issue for now or leave it open to be flagged as a long-term improvement. Martin |
Hi all,
I am posting this here, as this is likely a question which will come back several times and this issue can serve as documentation.
I would like to reconstruct a zoom simulation that was first generated with MUSIC, and start genetically modify it.
I believe that it is now potentially possible, by importing the white noise fields produced by MUSIC at the different levels using the “import_level_field” commands, with a syntax resembling
where 00009 would correspond to the basegrid. The following are the zoom levels which need to be opened manually at the right spatial position, and by factors of 2 to match the inner workings of MUSIC. Would you agree with that?
Another problem is that MUSIC produces the white noise files in binary format, compared to the required 3D-numpy input format for genetIC. Do you know of an existing tool to convert between these two formats? If yes, we could include it as part of the distribution.
Thanks in advance,
Martin
The text was updated successfully, but these errors were encountered: