-
Notifications
You must be signed in to change notification settings - Fork 29
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
New Extension: SpeciesType #180
New Extension: SpeciesType #180
Conversation
Left-over to do's from #177:
|
@ax3l There also should be a version number associated with this. I assume it should be 1.0.0 . |
@DavidSagan the version number will simply be the one of the standard it gets in with. |
85ed6e1
to
02320b7
Compare
OK just to make sure I understand: Say in the future changes to an extension necessitates that it is to be bumped up a version. Then even if the base standard has not changed it will be bumped up too? Yes? |
Exactly. |
@RemiLehe @marcguetg hi, do you want to give your review comments on this PR? From my side I think it's already in quite good shape. |
EXT_SpeciesType.md
Outdated
Additional Record Attribute | ||
--------------------------- | ||
|
||
The following additional attribute for openPMD `records` is defined in this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh wait, I think it should read:
... mesh records
and particle groups
...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about simply:
The following attribute for openPMD is defined ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, but I think for reader tools it is good to know where to look for it, no?
I currently only see these two locations as useful and relaxing later on is always possible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK I did not realize that this was defining where the info should go. How about adding a definition for mesh record
and particle group
in the Standard?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good, this aspect is moved to #187
@ax3l Should we merge this? |
ok, I addressed the last inline comment about the location of the |
Minor detail: Since |
Sure, we can do that. It's just not too common for us since it's neutral ;-) I did just draw a line (arbitrarily) since (anti-)protons are the only stable free hadrons. |
- file renamed to `EXT_SpeciesType.md` - extension name: `SpeciesType` with extension-ID `4` (`1` is used and we reserved `2`$ - formatting unified - defined `SpeciesType` as attribute: *recommended* if extension is declared - allowed `lists`, e.g. for a local *summed charge density* in a non-equilibrium plasma - atoms & isotopes: reference to IUPAC namings
Reference to the new extension `SpeciesType` in the base standard
- optional by default - clarify annotations
Not needed (yet)
Add pointers
8e781f6
to
c5c4733
Compare
@DavidSagan moved (anti-)neutron to "common" and added sigma baryon as another example. now we draw the line at the nucleus :D |
EXT_SpeciesType.md
Outdated
The following additional attribute for openPMD `mesh records` and | ||
`particle groups` is defined in this extension: | ||
|
||
- `SpeciesType` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wait, why is this upper-case in the first letter? Aren't we starting all attributes with a lowercase letter? Will update for consistency.
currently, all attributes start lower case.
@RemiLehe @DavidSagan I think this can be merged now :) |
An example would be `Si` for silicon. | ||
|
||
Specifications of isotopes are denoted by a pound symbol `#` followed | ||
by the isotopic number followed by the chemical symbol, e.g.: `#3He` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we add a mention on how to mention #2H2#15O
? It isn't fully clear how this works in this flow?
This pull request has a new file for standardizing the names of particle species.
Implements issue: #176
Description
This convention is for standardizing the names of particle species, e.g. in particle physics.
Affected Components
SpeciesType
Logic Changes
A new optional string attribute
speciesType
can now be present atmesh record
andparticle group
level.Writer Changes
openPMD-api
(upcoming): Add to writer and reader API.Reader Changes
Readers can if they want read the new attribute (if it exists) and propose e.g. groups, accumulations, etc. on it.
openPMD-validator
: Validate it's a string if present New Attribute: speciesType openPMD-validator#38openPMD-viewer
: https://github.com/openPMD/openPMD-viewer/...yt
: https://github.com/yt-project/yt/...VisIt
: https://github.com/openPMD/openPMD-visit-pluginopenPMD-api
(upcoming): https://github.com/openPMD/openPMD-api/...Data Updater
New optional extension with optional attribute. No update of existing data needed.
Edit: update needed for
ED-PIC
extension: #192