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

Plugin PhaseSpace - ranges missing in output files #381

Closed
PrometheusPi opened this issue Apr 29, 2014 · 6 comments
Closed

Plugin PhaseSpace - ranges missing in output files #381

PrometheusPi opened this issue Apr 29, 2014 · 6 comments
Assignees
Labels
component: plugin in PIConGPU plugin

Comments

@PrometheusPi
Copy link
Member

The *.h5 output of the phase space plugin does not include the ranges used.
Only the conversion from PIConGPU units to SI units is given as attribute f['data/2000/ypx'].attrs.get('sim_unit').

@ax3l
Copy link
Member

ax3l commented May 1, 2014

  • add ranges as attributes
  • only write data in window (tricky for momentum values, needs a more general solution with Plugins: analysis on selected window only #89) -> maybe write meta information to allow spatial alignment more easy like "where in this data set starts/ends the moving window"

@ax3l ax3l added the feature label May 1, 2014
@PrometheusPi
Copy link
Member Author

just as information:
There are more attributes in the *.h5 files than stated above: the header contains the attributes:

max_id
compression
mpi_size

But they do not describe the ranges used for the 2D histogram.

@ax3l
Copy link
Member

ax3l commented May 5, 2014

these information are libSplash intrinsics and do not correspond to user data :)

@f-schmitt
Copy link
Member

That's true, this data is written by libsplash.

ax3l added a commit to ax3l/picongpu that referenced this issue May 9, 2014
Uses m_species * c to scale output for now.
(Previously it scaled by the electron mass.)

New Attributes:
  - exclusive offset of the global moving window
    if the spatial dimension is == y
  - [p_min;p_max] + unit
  - dr + unit (spatial dimension)
  - dt + unit (time step)
ax3l added a commit to ax3l/picongpu that referenced this issue May 13, 2014
Uses m_species * c to scale output for now.
(Previously it scaled by the electron mass.)

New Attributes:
  - exclusive offset of the global moving window
    if the spatial dimension is == y
  - [p_min;p_max] + unit
  - dr + unit (spatial dimension)
  - dt + unit (time step)
@PrometheusPi
Copy link
Member Author

This seems to be a special case of the newer #408

@ax3l
Copy link
Member

ax3l commented May 13, 2014

#408 will be a generalization which might be done around the 1.0 release.

ax3l added a commit to ax3l/picongpu that referenced this issue May 13, 2014
Uses m_species * c to scale output for now.
(Previously it scaled by the electron mass.)

New Attributes:
  - exclusive offset of the global moving window
    if the spatial dimension is == y
  - [p_min;p_max] + unit
  - dr + unit (spatial dimension)
  - dt + unit (time step)
ax3l added a commit to ax3l/picongpu that referenced this issue May 13, 2014
Uses m_species * c to scale output for now.
(Previously it scaled by the electron mass.)

New Attributes:
  - exclusive offset of the global moving window
    if the spatial dimension is == y
  - [p_min;p_max] + unit
  - dr + unit (spatial dimension)
  - dt + unit (time step)
ax3l added a commit to ax3l/picongpu that referenced this issue May 14, 2014
Uses m_species * c to scale output for now.
(Previously it scaled by the electron mass.)

New Attributes:
  - exclusive offset of the global moving window
    if the spatial dimension is == y
  - [p_min;p_max] + unit
  - dr + unit (spatial dimension)
  - dt + unit (time step)
ax3l added a commit to ax3l/picongpu that referenced this issue May 21, 2014
Uses m_species * c to scale output for now.
(Previously it scaled by the electron mass.)

New Attributes:
  - exclusive offset of the global moving window
    if the spatial dimension is == y
  - [p_min;p_max] + unit
  - dr + unit (spatial dimension)
  - dt + unit (time step)
psychocoderHPC added a commit that referenced this issue May 22, 2014
Close #381 Meta Information in Phase Space
@ax3l ax3l closed this as completed in 3b1a1db Jun 4, 2014
ax3l pushed a commit to ax3l/picongpu that referenced this issue Aug 16, 2017
90ae873b9 Merge pull request ComputationalRadiationPhysics#382 from BenjaminW3/topic-CMake-3_9_followup
aad3f6a5e add missing changes to alpaka_add_library
d421e9a20 Merge pull request ComputationalRadiationPhysics#381 from BenjaminW3/topic-cmake-3_9
71fc4e7ed support CMake 3.9.0
441032e7f Merge pull request ComputationalRadiationPhysics#378 from ax3l/fix-uninitMemberMemcpy
dea0bd0f4 Merge pull request ComputationalRadiationPhysics#379 from ax3l/fix-warningCudaBraces
8643a97f0 cudaMemcpy3DParams: Fix Uninit Members
182d1b64f Refactor: double-braces for std::array init
a22e42a42 CUDA: Missing Initializer Warning
ddb2993aa Merge pull request ComputationalRadiationPhysics#375 from BenjaminW3/topic-update-readme
cf311c6a5 remove boost.context from ReadMe requirements
e93d5ae49 Merge pull request ComputationalRadiationPhysics#374 from BenjaminW3/topic-remove-boost-atomic-dependency
fe898716f remove unused boost atomic dependency
7a66700f2 Merge pull request ComputationalRadiationPhysics#371 from BenjaminW3/topic-duplicate-CUDA_NVCC_FLAGS
2f902cd70 Merge pull request ComputationalRadiationPhysics#372 from ax3l/topic-cmakeOptionalNoWarning
3f95afa83 CMake Config: Optional Deps
83a1bf3e6 Merge pull request ComputationalRadiationPhysics#369 from BenjaminW3/topic-clean-up-assertions
a932c02d7 clean up CUDA_NVCC_FLAGS
9753ef6fa clean up assertions

git-subtree-dir: thirdParty/alpaka
git-subtree-split: 90ae873b9984071e64343995e7721bde6a13ba7f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: plugin in PIConGPU plugin
Projects
None yet
Development

No branches or pull requests

3 participants