battery:addtestgitlab
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
battery:addtestgitlab [2025/10/29 10:10] arthur [Flowchart] |
battery:addtestgitlab [2025/10/29 10:57] (current) arthur [Creating your test] |
||
|---|---|---|---|
| Line 17: | Line 17: | ||
| If one of the steps goes wrong, the job fails and the user is not allowed to merge its modification. | If one of the steps goes wrong, the job fails and the user is not allowed to merge its modification. | ||
| - | ==== Main code ==== | ||
| - | * The principal python script to run the test battery: **Test_battery_launcher.py** | ||
| - | * The file defining the test battery path and the names of the tests in the same folder as the principal python script: **Test_battery.txt**. The structure of this file is shown in <imgref image3>. | ||
| - | <imgcaption image2|The pricipal script working directory>{{ :battery:file2.jpg |}}</imgcaption> | ||
| - | |||
| - | <imgcaption image3|Test_battery.txt file>{{ :battery:file3.jpg |}}</imgcaption> | ||
| ==== Tests ==== | ==== Tests ==== | ||
| - | The folder 'Tests' (see <imgref image4>) contains all the tests. \\ \\ | + | The folder 'Tests' contains all the tests. \\ \\ |
| - | Each test is in a separate folder named with the same name as the test defined in "Test_battery.txt". This folder contains: | + | Each test is in a separate subfolder named with the same name as the test defined in "Test_battery.txt", preceded by its number. For example, 26_HYPOFE2_KFLU1 is the 26th test in the battery, and it verifies the integrity of the law HYPOFE2 with parameter KFLU1. |
| - | * The simulation files (*.lag, *ex.dat, etc.) | + | |
| - | * The reference simulation in a folder with the same name as the test +"_ref" \\ **N.B.** this folder can contain only the result files (*.ipe, *.ipn, *.rea, ...) and not the totality of the simulation files, as they are the same as the test files. | + | |
| - | * A comparator python script attached to each test. This script must have the same name as its corresponding test. In the script, the user defines the numerical results to compare and the cost function. | + | |
| - | <imgcaption image4|Test_battery.txt file>{{ :battery:file4.jpg |}}</imgcaption> | + | In this test subfolder, there are: |
| + | - The necessary files to run the prepro and lagamine: .DAT, .LAG, .PRI, .DEP, .LIC, and so on. | ||
| + | - A subfolder named "ExpectedResults" in which the results file are: the .ipn, .ipe and .ipr. | ||
| - | ==== Output files ==== | + | No other file should be found in this subfolder. |
| - | __Local report__ \\ \\ | + | |
| - | The local report is attached to the test folder and has the same name as the test (name_test.rep). This local report contains the details of the error(s) obtained when comparing the new test results to the reference. \\ \\ | + | |
| - | It is structured as follows: | + | |
| - | * Local error | + | |
| - | * Decision (Success/ Failure): depending on the value of the error, the test is considered as passed or failed. The recommanded acceptance value for the error is 0.1% for a Mini test and 1% for a Big test. | + | |
| - | <imgcaption image5|Local report>{{ :battery:file5.jpg |}}</imgcaption> | ||
| - | __Global report__ \\ \\ | ||
| - | The global report is attached to the principal python script folder (Report_date.rep). \\ \\ | ||
| - | It contains the following information: | ||
| - | * Number of tests | ||
| - | * Global error | ||
| - | * List of tests | ||
| - | * Decision (Success/ Failure): once one test is failed, the whole test battery is failed | ||
| - | * List of failed tests (if the test battery is failed) | ||
| - | <imgcaption image6|Global report>{{ :battery:file6.jpg?700|}}</imgcaption> | ||
| - | \\ \\ | ||
| - | \\ \\ | ||
| ===== How to add your own test to the battery ===== | ===== How to add your own test to the battery ===== | ||
| ==== Creating your test ==== | ==== Creating your test ==== | ||
| Line 59: | Line 35: | ||
| In order to ensure that your developments in the Lagamine code will keep functioning properly, it is highly recommanded that you add one or several tests specific to the law(s) or element(s) you use and develop. \\ \\ | In order to ensure that your developments in the Lagamine code will keep functioning properly, it is highly recommanded that you add one or several tests specific to the law(s) or element(s) you use and develop. \\ \\ | ||
| To test a material law or an element, you should design a **simple test**, using only 1 element when possible. Preferably, your test should **not take more than a few seconds** to run. If you need to test something more complex, you can also create a "Big" test. However, the total number of Big tests should be limited to avoid excessive computational times for the whole test battery. \\ | To test a material law or an element, you should design a **simple test**, using only 1 element when possible. Preferably, your test should **not take more than a few seconds** to run. If you need to test something more complex, you can also create a "Big" test. However, the total number of Big tests should be limited to avoid excessive computational times for the whole test battery. \\ | ||
| - | //For instance, to test the visco-plastic 'CHAB' law, I created a test using a single element submitted to 2 cycles of alternated tension and compression (see [[battery:listtests:test7|CHAB_SC_TMF]]).// \\ | ||
| Once you have designed your test and created the necessary simulation files, you must identify the important variables that indicate whether your law/element is behaving as it should. \\ | Once you have designed your test and created the necessary simulation files, you must identify the important variables that indicate whether your law/element is behaving as it should. \\ | ||
| - | //For the 'CHAB' law, I will check the values of the stress tensor, the thermal strain, the plastic strain along the loading direction, and the damage variables. These values can be obtained via the [[appendices:a9|*.ipe result file]].// \\ \\ **Be sure to print out the values you want to check at the time step(s) you see fit**. \\ To define the time steps at which you want a printing, you can use [[lagamex:auto#rd_line_14i5_-_strategy_control_data|ILSAV = 1 or 2]] in the ex.dat file. \\ Check [[appendices:a1|Appendix 1: Printing options]] and [[appendices:a9|Appendix 9: Printing files]] for more info about printing files. | + | These values can be obtained via the [[appendices:a9|*.ipe result file]]. |
| - | + | ||
| - | ==== Comparator code ==== | + | |
| - | After you have created your test and identified the variables that need to be checked, you need to write the comparator code. \\ \\ This code should be written in a Python script. If Python is not already installed on your computer, you can download it from the official Python website: [[https://www.python.org/downloads/|https://www.python.org/downloads/]] \\ Several editors exist to facilitate coding and debugging with Python. You can use [[https://www.spyder-ide.org/|Spyder]] or [[https://code.visualstudio.com/|Visual Studio Code]] for instance.\\ | + | |
| - | For the comparator code, it is recommanded to use one of the existing comparators as an example. You can search in the Dokuwiki tests that use the same type of result files as you to find a code similar to what you should write. \\ | + | **Be sure to print out the values you want to check at the time step(s) you see fit**. \\ To define the time steps at which you want a printing, you can use [[lagamex:auto#rd_line_14i5_-_strategy_control_data|ILSAV = 1 or 2]] in the ex.dat file. \\ Check [[appendices:a1|Appendix 1: Printing options]] and [[appendices:a9|Appendix 9: Printing files]] for more info about printing files. |
| ==== Adding your test to the battery ==== | ==== Adding your test to the battery ==== | ||
| Line 73: | Line 45: | ||
| To add a new test to the battery, you should: | To add a new test to the battery, you should: | ||
| * Add the new test to "http://www.lagamine.uliege.be/dokuwiki/doku.php/battery/listtests" | * Add the new test to "http://www.lagamine.uliege.be/dokuwiki/doku.php/battery/listtests" | ||
| - | * Modify the file **Test_battery.txt** on Obelix: add the name of the new test | + | * Add the folder containing your test to the test battery directory. |
| - | * Add the folder containing your test to the test battery directory. This folder should contain: | + | |
| - | * The files of simulation (with the same name as the test) | + | |
| - | * The reference simulation folder (with the same name as the test + "_ref") | + | |
| - | * The comparator python script (with the same name as the test) | + | |
battery/addtestgitlab.1761729015.txt.gz · Last modified: 2025/10/29 10:10 by arthur
Page Tools
