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

Dump the assessments in the CSV files once they happen and not in the end of all executions #237

Closed
6 of 7 tasks
ruiAzevedo19 opened this issue Jul 3, 2024 · 2 comments
Closed
6 of 7 tasks
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@ruiAzevedo19
Copy link
Collaborator

ruiAzevedo19 commented Jul 3, 2024

TODO

1st iteration

  • Dump the assessments into the evaluation.csv every time a task is executed

2nd iteration

  • Create the other CSVs from the evaluation.csv
    • read evaluation.csv > sum the results > write to file
    • models-summed.csv
    • <language>-summed.csv

Follow-ups

@ruiAzevedo19 ruiAzevedo19 added the enhancement New feature or request label Jul 3, 2024
@ruiAzevedo19 ruiAzevedo19 added this to the v0.6.0 milestone Jul 3, 2024
@ruiAzevedo19 ruiAzevedo19 self-assigned this Jul 3, 2024
@bauersimon
Copy link
Member

bauersimon commented Jul 3, 2024

  • would basically just have only one evaluation.csv where everything is just dumped on the fly
  • the other two csvs can be created from the first one, it should just be different summing
    • thats also already the first step towards "combining multiple evaluations"
    • basically one single "raw" results file, and then we can do all the pretty stuff in a separate step
  • basically in this iteration you just read in the raw csv and do the summing up and write them out at the end of the evaluation

ruiAzevedo19 added a commit that referenced this issue Jul 4, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 4, 2024
…ing a task, to avoid losing information if the evaluation errors

Part of #237
ruiAzevedo19 added a commit that referenced this issue Jul 4, 2024
…, to avoid losing information if the evaluation errors

Part of #237
ruiAzevedo19 added a commit that referenced this issue Jul 4, 2024
…, to avoid losing information if the evaluation errors

Part of #237
ruiAzevedo19 added a commit that referenced this issue Jul 4, 2024
…, to avoid losing information if the evaluation errors

Part of #237
ruiAzevedo19 added a commit that referenced this issue Jul 4, 2024
…, to avoid losing information if the evaluation errors

Part of #237
ruiAzevedo19 added a commit that referenced this issue Jul 4, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 4, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 4, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 4, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 4, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 5, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 5, 2024
…, to avoid losing information if the evaluation errors

Part of #237
ruiAzevedo19 added a commit that referenced this issue Jul 5, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 5, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 5, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 5, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 5, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 5, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 8, 2024
…, to avoid losing information if the evaluation errors

Part of #237
ruiAzevedo19 added a commit that referenced this issue Jul 8, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 8, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 8, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 8, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 9, 2024
…aluation CSV file, since they are part of an evaluation record

Part of #237
ruiAzevedo19 added a commit that referenced this issue Jul 9, 2024
…aluation CSV file, since they are part of an evaluation record

Part of #237
ruiAzevedo19 added a commit that referenced this issue Jul 9, 2024
…fiers and repositories, since they are not needed for the summed values

Part of #237
ruiAzevedo19 added a commit that referenced this issue Jul 9, 2024
…aluation CSV file, since they are part of an evaluation record

Part of #237
ruiAzevedo19 added a commit that referenced this issue Jul 9, 2024
…fiers and repositories, since they are not needed for the summed values

Part of #237
ruiAzevedo19 added a commit that referenced this issue Jul 10, 2024
… they will be handled afterwards with tooling

Part of #237
ruiAzevedo19 added a commit that referenced this issue Jul 10, 2024
…med.csv" files, since they will be handled afterwards with tooling

Part of #237
ruiAzevedo19 added a commit that referenced this issue Jul 10, 2024
ruiAzevedo19 added a commit that referenced this issue Jul 12, 2024
… they will be handled afterwards with tooling

Part of #237
ruiAzevedo19 added a commit that referenced this issue Jul 12, 2024
…med.csv" files, since they will be handled afterwards with tooling

Part of #237
@bauersimon
Copy link
Member

remaining task will be implemented with #296

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

No branches or pull requests

2 participants