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

Particles: create a field from two dumpreader #117

Open
skuschel opened this issue Nov 14, 2017 · 2 comments
Open

Particles: create a field from two dumpreader #117

skuschel opened this issue Nov 14, 2017 · 2 comments

Comments

@skuschel
Copy link
Owner

skuschel commented Nov 14, 2017

Currently the createField methods are bound to a single dumpreader, that means its possible to create a field with different scalar quantities on each axis. e.g.: plot 'gamma' over 'x'.
It is currently impossible to create a field from multiple dumps, e.g.: 'x in dump 200' over 'x in dump 2'. This requires to pick identical particles from both dump AND return them in the same, but arbitrary order.

  • Probably good to find a way to "equalize"(find better word?!) two dumpreader to do exactly that.
  • Concept and desired interface needed for creating the plots.
@skuschel skuschel added Field core routines affected needs discussion labels Nov 14, 2017
@skuschel skuschel added this to the v1.0 milestone Nov 14, 2017
@skuschel skuschel added this to Possible issues in Institute Hackathon 171121-22 via automation Nov 14, 2017
@skuschel skuschel removed the Field core routines affected label Jan 30, 2019
@skuschel
Copy link
Owner Author

Demo for matching particles with identical IDs from different dumps is here (remove .txt):
postpic particle matcher.ipynb.txt

@skuschel
Copy link
Owner Author

skuschel commented Jan 25, 2024

Probably having a new function postpic.particles.createField which takes the form ((ms1, exp1), (ms2, expr2), ....).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Institute Hackathon 171121-22
  
Possible issues
Development

No branches or pull requests

1 participant