You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason these are not documented is because the properties associated with the trm data are generated on the fly on import since there are so many of those quantities and they may not exist for each HYDRAD run.
Since these properties are all known (unlike, say, the NEI fractions which vary according to the simulation setup), we could hardcode all of these docstrings similarly to what is done for some of the other properties. This would be overly verbose and would make the parse.py file quite long.
Alternatively, there may be some way to auto-generate these docstrings not at import such that they would be included in the rendered docs. Off the top of my head, I'm not sure how to do this, though I think it is possible.
After #169, we added a parsing of all the data in the
.trm
files, but we did not add their descriptions to the Docs.(https://pydrad.readthedocs.io/en/latest/api/pydrad.parse.Profile.html)
The text was updated successfully, but these errors were encountered: