-
Notifications
You must be signed in to change notification settings - Fork 4
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
Adding category examples #124
base: master
Are you sure you want to change the base?
Conversation
…omponent_presentation_order
No examples in the category directly, but have pointed to other examples which use PD_QPA_OVERALL.
as per rule 2.3
the second example may be a little long-winded...
I don't think that '_pd_calib_detected_intensity.id' is a necessary category key.
I don't think that
|
I think we should keep If I have
then I think this ties in to #163. This whole argument also applies to * I need to add a key to |
Adding examples of use at the category level.
Not updating update dates yet.
Categories:
PD_AMORPHOUS
PD_BACKGROUND
PD_BLOCK
_pd_block.id
, but it's the only member.PD_CALC_COMPONENT
PD_CALC_OVERALL
PD_CALIB_D_TO_TOF
PD_CALIB_DETECTED_INTENSITY
PD_CALIB_INCIDENT_INTENSITY
PD_CALIB_WAVELENGTH
PD_CALIB_XCOORD
PD_CALIBRATION
PD_CHAR
PD_DATA
(containingPD_CALC
,PD_MEAS
,PD_PROC
)PD_DIFFRACTOGRAM
_pd_diffractogram.id
, but there're only two members.PD_INSTR
PD_INSTR_DETECTOR
PD_MEAS_OVERALL
PD_PEAK
PD_PEAK_OVERALL
PD_PHASE
PD_PHASE_MASS
PD_PREF_ORIENT_MARCH_DOLLASE
PD_PREF_ORIENT_SPHERICAL_HARMONICS
PD_PREP
PD_PROC_LS
PD_PROC_OVERALL
PD_QPA_CALIB_FACTOR
PD_QPA_EXTERNAL_STD
PD_QPA_INTENSITY_FACTOR
PD_QPA_INTERNAL_STD
PD_QPA_OVERALL
PD_SPEC
Not (currently) going to, as other categories are taking over, or have taken over:
PD_BLOCK_DIFFRACTOGRAM
PD_CALIB
PD_CALIB_OFFSET
PD_CALIB_STD
PD_MEAS_INFO_AUTHOR
PD_PHASE_BLOCK
PD_PREF_ORIENT
PD_PROC_INFO_AUTHOR