-
Notifications
You must be signed in to change notification settings - Fork 120
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
Different Meshscalings #195
Comments
Hi This is quite a technical accomplishment and it is not something which is implemented for the moment but it should be technically possible with python manipulations only. |
I would say it is currently unrealistic. The tricks suggested by @beck-llr are really complicated. We could imagine a new feature in which the restart from a checkpoint would use a different mesh resolution, but this is quite a challenge. One difficulty is to treat correctly the boundary conditions for fields. Note that, for TNSA, it is unclear for me how the evolution of fields due to the dense target expansion will affect the accelerated ions. I am not sure you can safely discard the dense target and use a low resolution. In addition, the accelerating field is created by escaping electrons, which are affected by the 2D geometry : only 3D will accurately describe them. Thus this seems quite a stretch to try to simulate late-time evolution in 2D. |
To build up on the answers by @beck-llr and @mccoys I would say that: |
There was a publication by Z. Lecz et al. at ICAP 2012 [1],[2], where the assumption of a drifting plasma after a specific acceleration time allows for a coarser \Delta x and \Delta t meshing. Cheers, [1] https://accelconf.web.cern.ch/accelconf/ICAP2012/papers/frsai3.pdf |
Heyho,
I am currently trying to setup some TNSA calculations.
As long as the laser is interacting with the plasma a very fine mesh is needed. (Have to resolve the laser parameters).
Afterwards to see how the particles drift on a coarser mesh is possible to decrease the amount of data that needs to be saved.
Is there any way to do this properly in smilei?
I thought about the checkpoints utility, but it states that it needs the same input file. Which then also uses the same fine mesh again?
Is there something I did not find yet? Or is it not possible to change this calculation domains?
The text was updated successfully, but these errors were encountered: