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

Relative Global Domain Position for Density Profiles #3598

Open
n01r opened this issue Apr 20, 2021 · 1 comment
Open

Relative Global Domain Position for Density Profiles #3598

n01r opened this issue Apr 20, 2021 · 1 comment
Labels
component: core in PIConGPU (core application) component: examples PIConGPU or PMacc examples component: user input signals changes in user API such as .param files, .cfg syntax, etc. - changelog!

Comments

@n01r
Copy link
Member

n01r commented Apr 20, 2021

I think it would be really helpful if we had an easy option of accessing the relative global domain position in density profiles.
It exists already partly for particle filters where RelativeGlobalDomainPosition allows to give an upperBound and a lowerBound (a free number of boundaries and logical connections between them is not yet possible).

This would make it much easier to place slices and boxes of e.g. probes and tracers somewhere.

@n01r n01r added component: core in PIConGPU (core application) component: examples PIConGPU or PMacc examples component: user input signals changes in user API such as .param files, .cfg syntax, etc. - changelog! labels Apr 20, 2021
@n01r n01r added this to the 0.6.0 / 1.0.0: Next Stable milestone Apr 20, 2021
@sbastrakov
Copy link
Member

@n01r perhaps that is possible already? Imagine you have such a custom density functor that accepts relative position in its operator(). You then write another density functor inheriting yours. In the constructor of that new functor (it is done on the host anyways) you can access Environment and get domain data there, save it in members. Then in the operator() you use this data to convert totalCellOffset to relative position, and call the operator() of the base class (your original functor). It is true we can, and probably should, provide smth like that. But in principle this should be doable fully externally

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: core in PIConGPU (core application) component: examples PIConGPU or PMacc examples component: user input signals changes in user API such as .param files, .cfg syntax, etc. - changelog!
Projects
None yet
Development

No branches or pull requests

3 participants