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

Standardize Universe Design to Enable University History and Jupyter Notebook Usage #7836

Closed
3 tasks done
jaredbroad opened this issue Mar 7, 2024 · 0 comments · Fixed by #7837
Closed
3 tasks done

Comments

@jaredbroad
Copy link
Member

Expected Behavior

Universes follow a reasonably predictable pattern despite the different formats of data available.

Actual Behavior

We have multiple variants of universes to its difficult to make a history call or use them in jupyter notebooks.

Universes styles include:

  • A1 WrapperForBaseDataUniverses - Where the wrapper sets configuration and the selection is done on another type.
  • A2 BaseDataUniverses - Where there's just the base data type; and the selection-filtering is done on that same basedata object.

These universes output 2 types of data in the slice:

  • B1 - BaseData Objects - Where the universe outputs a single point representing the selected symbol. e.g. Weather in a location at a point in time,
  • B2 - BaseDataCollection Objects - Where the universe can select multiple objects that occur at the same time; e.g. a news feed with multiple simultaneous posts.

Potential Solution

Review and standardize naming across all the fundamental data, universe alternative data classes. It might need breaking some of the smaller data types.

Then this will enable full use of any alt data universe for history calls on universes and jupyter notebook usage.

Checklist

  • I have completely filled out this template
  • I have confirmed that this issue exists on the current master branch
  • I have confirmed that this is not a duplicate issue by searching issues
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants