You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Below are issues affecting the rc1 data release that cannot be fixed without a data update. As updating is disruptive (it'll break code and make results non-comparable), it should be done sparingly, e.g., to fix a fatal flaw or many small ones discovered over time.
The master branch contains the code that produced the latest released data. The usage code and documentation can be updated but should work with the released data.
The next branch contains the code to produce the hypothetical next release of the data. The usage code is updated to any new data format.
The outputs branch is based on master and contains generated data (e.g., notebook outputs and figures) for convenience (most notably to run on binder).
Activity
[-]Known issues and next release[/-][+]Known issues (and next release)[/+]mdeff commentedon Jun 17, 2020
Branches:
masterbranch contains the code that produced the latest released data. The usage code and documentation can be updated but should work with the released data.nextbranch contains the code to produce the hypothetical next release of the data. The usage code is updated to any new data format.outputsbranch is based onmasterand contains generated data (e.g., notebook outputs and figures) for convenience (most notably to run on binder).mdeff commentedon Jun 17, 2020
Potential todos for a dataset update:
tracks.csv,artists.csv,albums.csv) instead of a single hugetracks.csv? Consider standards like JAMS.