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

separate metadata and trace data #175

Open
jonorthwash opened this issue Oct 2, 2022 · 1 comment
Open

separate metadata and trace data #175

jonorthwash opened this issue Oct 2, 2022 · 1 comment
Assignees
Labels

Comments

@jonorthwash
Copy link
Collaborator

Currently metadata and traces are both stored in metadata.json.

This can be problematic, because sometimes the metadata needs to be refreshed (e.g., when working on data in a new directory, because of #156), which can currently only be done manually or by deleting the file (#152).

It would be nice to have metadata.json for everything but traces, and traces.json for traces. At least one of the files should track the other–probably at least the former should have the filename of the latter, maybe replacing a traces datatype with a traces_filename field, for most robust compatibility.

@Quaratz13
Copy link
Collaborator

Quaratz13 commented Mar 31, 2023

Overview:

  • manually separate files (metadata and traces file) (include traces file in metadata)
  • write code to load the new traces file
  • write code to check if old or new type and decide which method to use to load it
  • write code to separate the file types (if it's all in the old metadata file)
  • prompt user if they want the files separated or use the old type)

@Quaratz13 Quaratz13 self-assigned this Mar 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants