-
Notifications
You must be signed in to change notification settings - Fork 10
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
New group for information on simulated phantoms #43
Comments
actually this is quite similar to what is contained in the reconstruction group, no? This is how it once was implemented in IMT framework, i.e. that phantom and reconstruction data have the same file format. |
Yes, precisely - it still is implemented like that ;) So to use MDF with our complete simulation chain a phantom group would be nice. It would be a workaround to use reconstruction, if a new group would be too irretating for other MDF users. |
No actual preference on this one, but I think we could factor phantom (geometry) and tracer (material) into one/two separate groups (as they are closely related anyway). |
This is an area where MDF is indeed not so well designed for. Our primary use case is to destribute measurment data. Feel free to make proposals how the MDF can improve in that area! best is to work on the tex file and make pull requests that can be discussed. |
For simulations it is necessary to have information about the phantom used. That is why it would be great to have an optional group phantom with a paramter data. I have to admit that currently this is the only parameter necessary. But I think it would be wise to have a specific group phantom rather than putting it in some other group. The only group where it might be possible is tracer, but I think having the phantom as tracer property would be misleading. I'm open for further suggestions.
The text was updated successfully, but these errors were encountered: