Benchmarks should be Samples #56304
Labels
No Label
Priority::High
Priority::Low
Priority::Normal
Status::Archived
Status::Confirmed
Status::Duplicate
Status::Needs Information from Developers
Status::Needs Triage
Status::Resolved
Type::Bug
Type::Design
Type::Report
Type::To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/blender-open-data#56304
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Open Data platform aims at hosting more than benchmark results. For this reason we should look into introducing a more generic data structure, called 'sample'.
Sample schema on My Data
A similar schema could be adopted by Open Data
AlphaID vs UUID
While it would be fantastic to be able to reference a sample with a 6-chars alphanumeric string, which would be build starting from the My Data sample id, we understand that the Open Data portal will get data input from various sources. This issue can be solved by providing a 'serie' name with the sample.
Added subscriber: @fsiddi
Added subscriber: @SemMulder
I think a better approach would be to create different specific (i.e. non-generic) data structures for different kind of samples. I believe this to be a better option because statically known data structures are easier to reason about than dynamic ones (especially if combined with type checking), resulting in more robust code.