-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add additional waveform signal to IOD definitions #53
Comments
Thanks, Brian, for getting this started. I've added these to the code, untested, however. A few questions:
We also need to update units: UCUM_ENCODING = { Ultimately, I need to cite the source vocabulary for the waveform names and the units. But for now, I've just filled in some values if i didn't know them. Finally, the code currently does not enforce the limits on number of multiplex groups, number of channels in each group, maximum number of samples and frequency ranges. ( the test case did not hit the limits) Let's see if the rest of the test data creates problems. Updates (untested) checked in. |
Also, i have some Emory GE data in WFDB format. Spot checking them shows the following channel names: I assume CVP1 is same as CVP. Not sure about CVP2, AR1, AR2, and PA2. |
Yes.
From what I read online, the MCL lead is independent and isn't usually grouped with other leads.
I don't see information regarding which lead this comes from in the project descriptions.
Based on the result from #11 (comment) : hemodynamic: sleepEEG: Respiratory:
Ok, thanks
This is what I see for units for the new signal types:
Where were your untested updates checked in? |
I also can't tell from searching online what the difference between CVP (Central Venous Pressure), CVP1, and CVP2 are. Similarly for AR1 and AR2 which are arterial waveforms. PA2 is a pulmonary artery waveform. |
My engineer did a scan through our existing WFDB files for channel names. Below is the aggregated list. I am checking internally also for meaning of the names. I have not checked in these as the inclusion of canonical name is going to require code change.
|
@tcpan , thanks for generating a comprehensive list. My thought is that we should focus on the signal types that you and I noted further above that came from the waveform suite of files we are using for benchmarking. These signal types come from the 40 files here ( #11 (comment) ) and 10 of the files you've provided. That will enable me to run the official benchmarking on the DICOM format. We could continue to update your code after the benchmarking is done to add additional signal type to IOD mappings. What do you think? |
Agree with the plan. |
We need to add additional mappings between a waveform signal type and a DICOM IOD. In some cases we need to add the code for the IOD to the
dcm_waveform_writer.py
file:I've attempted to create a complete list of the signal type to IOD mappings for all signal types in our benchmarking waveform suite ( #11 (comment) ) :
I guess the CO2 object should map to some kind of "Exhaled Gas IOD"
The text was updated successfully, but these errors were encountered: