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

Original vs processed data #206

Open
jepegit opened this issue Apr 18, 2022 · 0 comments
Open

Original vs processed data #206

jepegit opened this issue Apr 18, 2022 · 0 comments
Milestone

Comments

@jepegit
Copy link
Owner

jepegit commented Apr 18, 2022

It would be handy to have two levels of data:

  1. the actual raw-data and step table (and maybe summary data).
  2. processed data - e.g. data that has been cleaned and maybe interpolated.

Things to consider:

  • use some hashing algorithm to compare processed vs actual
  • be able to revert to the original raw data
  • how will this work when allowing to do c.update()?
  • keep track of the processing steps
c.is_original()  # True if data is not tweaked
c.revert_to_original(option="some-option")  # reset to original (actual data)
c.save(fname, only_original=True)
c.save(fname, only_processed=True, overwrite=False)  # make a new cellpy-file containing only processed data (with a new filename e.g. original_filename_ed001.h5)
c.load(fname, only_original=True)

# Not first priority:
c.to_SOME_FORMAT(original=True, processed=True)
c.history()  # prints the commands used to tweak the raw data.
@jepegit jepegit added this to the v.1.0.0 milestone Apr 18, 2022
@jepegit jepegit modified the milestones: v.1.0.0, v.1.1.0 Jan 23, 2023
@jepegit jepegit modified the milestones: v.1.1.0, v2.0.0 Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant