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

Need to define formatting code #1

Open
gnperdue opened this issue Oct 8, 2019 · 2 comments
Open

Need to define formatting code #1

gnperdue opened this issue Oct 8, 2019 · 2 comments

Comments

@gnperdue
Copy link

gnperdue commented Oct 8, 2019

We pull down data in one set of formats, and need to re-format them for training and testing purposes. We should clearly define theses transformer codes.

Longer-term, we need to be sure that the low-latency data streams are logged in a compact fashion. These may also require transformer codes (may not be associated with the workflow repo).

@jasonstjohn
Copy link
Collaborator

I anticipate changing the data format we initially store. We could go directly for something which might be used "as-is" for training/testing/etc or, if that also seems likely to change, some in-between format which is readily converted. If the latter approach is adopted, modularizing our data flow has its advantages, and I would be happy to work on the second phase in data processing.

@gnperdue
Copy link
Author

This issue may be subsumed by fermilab-accelerator-ai/meetings#31 - if we do move to a SQL server long term, then of course we need to define the correct tables, etc.

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