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

Discussion about dataformat #24

Open
gvannoye opened this issue Jun 11, 2021 · 1 comment
Open

Discussion about dataformat #24

gvannoye opened this issue Jun 11, 2021 · 1 comment

Comments

@gvannoye
Copy link

Here are the dataformats I suggested during one of the Virtual Offices:

proposed formats:

AlertObservation:
detector_name: str that must be in a list of detector names
sent_time: str in the format of "YYYY-MM-DD hh:mm:ss ns" (precision to the ns not needed?)
event_time: str in the format of "YYYY-MM-DD hh:mm:ss ns"
detector_status: str that must be in a list of possible status (to be determined with the experiments)
FAR? FAR-tier?

should the FAR-tier be included in the content of the message, 
or should two models (with different ids) be made for SNEWS-LOW and SNEWS


SignificanceObservation:
content of AlertObservation
p-value: float


TimingObservation:
content of SignificanceObservation
time-series: two possibilities, reconstruction of single events or distribution

two models to include those two possibilities?

reconstruction of single events: 
{channel1: {id1: {time: time1, energy: energy1}, id2: {time: time2, energy2}}, channel2: …}

distribution of binned events:
{list of times, list of number of events}

There are also some other questions I will put as other issues, and reference them here.

@habig
Copy link
Contributor

habig commented Jun 11, 2021

The way forward on this is to define classes that have all the data format items we want in them. The same class to be used at both ends (experiment client and server), and the class will handle the way it writes itself out to the hop stream, reads itself in and verifies that it read in correctly.

There's an issue about this somewhere, which I'll try to find and link in here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants