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

Integrating MRI acquisition assays into OBI #1760

Open
adbartni opened this issue Jan 11, 2024 · 6 comments
Open

Integrating MRI acquisition assays into OBI #1760

adbartni opened this issue Jan 11, 2024 · 6 comments
Assignees
Labels
dev:input wanted assignee requests input from others to address issue

Comments

@adbartni
Copy link
Contributor

Hello, and thank you for your cooperation in incorporating many of our MRI classes into OBI thus far (#1481). We have several more classes we would like to contribute, mostly pertaining to the acquisition of MRI data. These are subclasses of magnetic resonance imaging assay and largely correspond to image data set subclasses that have already been added to OBI. For example, a proposed class T1 weighted imaging acquisition sequence has as specified output T1 weighted image data set (OBI:0003341).

Below is a screenshot from Protege of the structure of MRI acquisition terms we would like to contribute:

mrio_assays

Unlike the image data set classes that we have already integrated with OBI, these image acquisition assays use logical axioms to describe the parameters keyed into an MRI machine to acquire a specific kind of MRI data. These classes also use data properties that we have defined in MRIO to describe the process of acquiring MRI data. Below is a screenshot of Protege of an example of these properties used to define the acquisition of a T1 weighted image data set.

t1w_acquisition_params

As such, we would like to discuss whether such specific classes are appropriate for OBI, or whether we should make them more generic at higher levels with the ability to create subclasses that use specific data properties.

We would be happy to discuss during the OBI developer meeting.
Thanks!
Alex Bartnik and Alex Diehl

@ddooley
Copy link
Contributor

ddooley commented Jan 22, 2024

Discussing in Jan 22 call: Issue is degree to which OBI wants to take on MRI specific data properties. Is it possible for MRIO to enhance OBI classes with these properties? The specificity of modelling creates a challenge for OBI. But we're aware that this is an incentive for adding them to MRIO directly... but this runs the risk of maintenance issues in the MRI domain in the future? Can you comment on ability to define data properties on your side, after reusing OBI MRI classes in MRIO?

@addiehl
Copy link

addiehl commented Jan 29, 2024

After discussion on Jan 29 OBI call, MRIO developers will submit generic versions of the subclasses of 'magnetic resonance imaging assay' class to OBI that do not rely on the MRIO data property axioms but do include additional information in their textual definitions that capture some of the information in the MRIO logical axioms.

@bpeters42
Copy link
Contributor

@addiehl - checking in on the status of this?

@addiehl
Copy link

addiehl commented Apr 29, 2024

This will be coming in the next couple months.

@mgiglio99
Copy link
Contributor

Hi @addiehl just checking if there are any updates on this.

@addiehl
Copy link

addiehl commented Jul 29, 2024

We are working on the MRI terms actively, and I will see if we can get the OBI submission together soon.

@DanBerrios DanBerrios added the dev:input wanted assignee requests input from others to address issue label Dec 18, 2024
@DanBerrios DanBerrios assigned addiehl and unassigned DanBerrios Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev:input wanted assignee requests input from others to address issue
Projects
None yet
Development

No branches or pull requests

6 participants