Next: Models, Previous: Output files, Up: Top [Contents]
Bil produces some files and sometimes can read and use some other files. The name of these files are formed with the name of the input data file and suffixes, my_file.suf, in the same way as the output files. They are listed in the table below.
| fichier | description |
| my_file.ti | output files related to date index i |
| my_file.pi | output files related to point index i |
| my_file.posi | view i to be read by Gmsh |
| my_file.msh | Gmsh mesh file |
| my_file.graph | mesh graph |
| my_file.graph.iperm | inverse permutations file |
| my_file.sto | storage file |
| my_file.cont | continuation file (see below for explanations) |
| my_file.conti | continuation file (see below for explanations) |
The files my_file.cont and my_file.conti allow to continue a previous computation or to resume an interrupted calculation achieved with a previous input data file (my_previous_file). With my_file.cont the process doesn’t go through the initialization stage (ComputeInitialState, see below) so that the calculation continues as if there hadn’t been interruption. With my_file.conti the process goes through the intitialization stage so that some variables of the model can be re-initialized (e.g. strain variables can be reset to zero). To do so, copy the file my_previous_file.sto in my_file.cont (or my_file.conti) and run bil with my_file as a new input data file in which you will have defined some additional dates beyond the last date defined in my_previous_file.