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

the "store everything" function #137

Open
dneise opened this issue Feb 26, 2018 · 0 comments
Open

the "store everything" function #137

dneise opened this issue Feb 26, 2018 · 0 comments

Comments

@dneise
Copy link
Collaborator

dneise commented Feb 26, 2018

I've seen some discussion about storage of analysis results and events and so on.

I just realize, that this is something, which we might get from ctapipe for free, if we use the containers correctly.

By correctly I mean the opposite of what I just recently said in a different discussion. So you see, I am often totally lost. :-(

Anyway, I think we agree. We are slowly running into the situation where we have too much custom code for storing data, which leads to files, which can only be read, when closely reading the code, which wrote the files... I think we agree, we would like to avoid that.

At the moment I see two different types of output:

  1. event-wise
  2. cumulative.

For the event-wise output I think we can profit from ctapipe. I'll review their current status and try to propose something. Of course, one often does not want to store the entire event, so a useful solution needs to be able to provide some description like: "store everyting, but not the adc_samples" ... or so.

For the "cumulative" output an example would be the output generated by io.save_bias_curve or io.save_adc. And I have at the moment no idea how to generalize this. So I'd say for this part we just keep on doing whatever we like, and see how it goes. (I need to prevent myself constantly from "overdesigning" ... )

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

2 participants