-
Notifications
You must be signed in to change notification settings - Fork 33
Open
Labels
maintenanceCode maintenance taskCode maintenance task
Description
Currently we only check that the input files run correctly, but we are not checking if they actually produce expected answers.
The table below summarizes if tutorials produce some output that can be used to check that they keep producing the expected answer or not
| name | checks |
|---|---|
✅ prints n_octants and n_dir_per_oct |
|
| outputs data into a file -> then displays a plot | |
✅ prints eigen_value |
|
✅ prints ratio |
|
✅ prints forward_total_flux,response |
|
✅ prints adjoint_total_response |
|
✅ prints forward_total_flux,response |
|
| ✅ prints total_response_detector | |
| ✅ print total flux and response | |
| produces a plot | |
| no ckecking | |
| exports pvtu file | |
| exports pvtu files | |
| exports pvtu file | |
| exports pvtu file | |
| exports pvtu file | |
| exports pvtu file | |
| exports pvtu file | |
| exports pvtu file | |
| ✅ prints several things | |
| ✅ prints several things | |
| ✅ prints several things | |
| ✅ prints several things |
Mostly the mesh tutorials just produce a mesh file. Maybe, we could print number of nodes/cells for those?
The checkmarks indicate that there is something in the tutorial that could be used by the testing system to make sure the expect anser is produced by the code.
Metadata
Metadata
Assignees
Labels
maintenanceCode maintenance taskCode maintenance task