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

Observed data as References #46

Open
Yuri05 opened this issue Nov 12, 2019 · 0 comments
Open

Observed data as References #46

Yuri05 opened this issue Nov 12, 2019 · 0 comments

Comments

@Yuri05
Copy link
Member

Yuri05 commented Nov 12, 2019

The main goal is: additionally to the storage of observed data as part of PK-Sim/MoBi project (Status Quo): enable storage of only the Reference to the corresponding data source, e.g.:

Suggested workflow:

  • 2 Import modi should be available in PK-Sim/MoBi: „Import as data“ (=status quo) and „Import as reference
    • Import mode can be changed under program options
    • PK-Sim/MoBi check at every program start if the Import mode was saved in the user options. If not: user is prompted to set the option explicitly (same program behavior as in case of chart watermarks)
  • When new observed data is imported: Import mode used during the import is saved for every imported data set.
  • In case of „Import as data“ – no changes to the status quo. Imported data is saved as part of the project and reloaded from project when it’s opened (no connection to the original data source is required anymore)
  • In case of „Import as reference“:
    • When importing from new data source: checksum of the data source is calculated and saved for every imported data set:
    • When closing a project: all ObservedData with import mode „Reference“ will NOT be saved. Only the reference to the used data source and import settings are saved in the project.
    • When opening a project: all ObservedData with import mode „Reference“ are automatically reimported (based on the saved data source reference and import settings)
      • If data source is not available: observed data sets will be shown as “Missing” (+ Warning is shown to the user)
        • To be discussed: how to proceed with Simulations/Comparisons/PIs using Missing observed data sets
      • If data source is available but the data was changed (e.g. perform CheckSum-comparison): observed data sets will be shown as “Changed” (+ Warning is shown to the user)
        • To be discussed: how to proceed with Simulations/Comparisons/PIs using Missing observed data sets
    • When exporting: only ImportConfiguration+ReferenceToDataSource+Checksum is exported, but not the data itself. This applies to:
      • Export project as snapshot
      • Export PI to Matlab/R
      • Save ObservedData in Working Journal
      • Save ObservedData as pkml
      • Save ObservedData as template
      • When exporting observed data to file (excel, csv, …): the data is exported

Additionally:

  • It should not be possible to edit observed data in projects anymore. In case of changes: “Update data set from a new data source” workflow should be used instead
  • It should be possible to make a data set imported in “Reference” mode persistable in project (means: data will remain in project)
@Yuri05 Yuri05 added the Roadmap label Nov 12, 2019
@Open-Systems-Pharmacology Open-Systems-Pharmacology locked and limited conversation to collaborators Nov 12, 2019
@Yuri05 Yuri05 removed the Roadmap label Nov 21, 2022
@Yuri05 Yuri05 moved this to Under discussion (technically feasible; open for sponsorship) in OSP Suite Software Roadmap Dec 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Status: Under discussion (technically feasible; open for sponsorship)
Development

No branches or pull requests

1 participant