Skip to content
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

Adjusting gridGlobalOffset and temporal offset #708

Open
sjgrimm opened this issue Apr 5, 2024 · 7 comments
Open

Adjusting gridGlobalOffset and temporal offset #708

sjgrimm opened this issue Apr 5, 2024 · 7 comments
Labels
feature-request something that could be added to the code

Comments

@sjgrimm
Copy link

sjgrimm commented Apr 5, 2024

Hello,

I would like to be able to set the dimensions of the simulation box at arbitrary values for x,y,z (e.g. xmin = -40um, xmax = 40um, ...) and also start the simulation at different times (e.g. t=-100fs). This would allow the users to always keep a point of interest (e.g. laser focus) at the same position (e.g. (0,0,0) with time of laser irradiation at 0fs).

I think that this should be relatively easy to implement, as all parameters are already there in order to satisfy the openPMD standard. Additionally, the moving window already kind of uses this feature.

Thank you for your assistance!

@sjgrimm sjgrimm added the feature-request something that could be added to the code label Apr 5, 2024
@sjgrimm
Copy link
Author

sjgrimm commented Apr 5, 2024

Or is there a way to manually change values in the hdf5 via a command in the namelist?
Then I could use this as a workaround and manually set the desired values for gridGlobalOffset and the temporal offset.

@mccoys
Copy link
Contributor

mccoys commented Apr 5, 2024

This can be done at post-processing time using happi:
https://smileipic.github.io/Smilei/Use/post-processing.html#other-arguments-for-diagnostics
arguments xoffset, yoffset

@OwenSlevert
Copy link

I have the same problem. It would be really helpful, if it could be implemented before starting the simulation.

@mccoys
Copy link
Contributor

mccoys commented Apr 5, 2024

Why do you need it at the beginning if it can be changed afterwards?

@sjgrimm
Copy link
Author

sjgrimm commented Apr 5, 2024

I am interested in a solution that works before post-processing. The proposed solution with happi goes against all efforts of the openpmd standard.
Therefore, I would highly appreciate if you could add this feature (or propose some kind of workaround that works before post-processing).

@sjgrimm
Copy link
Author

sjgrimm commented Apr 5, 2024

I want to be able to use the same tools for visualisation for all my simulations (also independent of the code they were compiled with). Thats what the openpmd standard is for...
https://github.com/openPMD/openPMD-standard

@beck-llr
Copy link
Contributor

beck-llr commented Apr 5, 2024

One could argue that defining an arbitrary offset should be done during post-processing and not pre-determined and definitive because you might want to change your mind and be able to use different offset for the same data.

So maybe a request on the side of the viewer you are using to implement xoffset and yoffset as in Happi would be relevant ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request something that could be added to the code
Projects
None yet
Development

No branches or pull requests

4 participants