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

Adding Software Version to Device Usage #508

Open
Peyman-N opened this issue Jul 4, 2024 · 3 comments
Open

Adding Software Version to Device Usage #508

Peyman-N opened this issue Jul 4, 2024 · 3 comments

Comments

@Peyman-N
Copy link
Member

Peyman-N commented Jul 4, 2024

During the review of the neuroimaging extension, MRIScannerUsage, we encountered a problem: most of the scanners have software associated with them. I created this issue to follow up on that discussion.

Luyba:

Question: MRI scanners are always used in connection to a software version (which is functioning as device control system and performs online image processing). I would suggest to link to the Software Version that was used during the Device Usage. Do we need this for all devices as option or is this something scanner specific?

Peyman

Completely agreed. I think adding it to the concept of device usage is more beneficial. There are cases where the device usage doesn't have any software associated with it, for example, the usage of a microtome. However, I think it is present in enough cases to consider it. Anyway, this seems like an important issue and needs more discussion, so I created an issue on OpenMinds-Core to discuss it further.

@lzehl
Copy link
Member

lzehl commented Jul 4, 2024

follow up question: I assume that the software version or even software could be changed using the same scanner / device (I know that his would be also true for blackrock acquisition systems for example).

@jcolomb
Copy link
Contributor

jcolomb commented Jul 4, 2024

What about the firmware and firmware version ?

We have the instrument (physical object), following some hardware specification, and running some firmware (code that is essential to the activity of the instrument and is loaded inside the instrument), and software (code running of the computer controlling the instrument and usually doing some data preprocessing.

In theory, each one can be versioned and get a PID (instrument /physical object, hardware type, firmware, software)

@lzehl
Copy link
Member

lzehl commented Jul 4, 2024

@jcolomb this is a good point. so far I would have categorized firmware as software to be honest (just not running on a users computer but directly as part of the hardware). we will discuss if a distinction in schema is required or if software just needs a specification (on where it can be run which I think we partially do already)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants