Saving a current session

            When you have finished your Gambit session, go on the  menu items file - SaveAs and just enter the name of your session. It seems that you can give a title to the session (different from the id) but it is maybe easier in a first time to keep same names everywhere.
             Once the session is saved, you have to export it in order to create the right file to be read by the solver you have chosen. To do so, just go on file-export-mesh. If the solver is Fluent, you will have a file in .grd.
 
 

Session files

            When you have saved your Gambit session, Gambit creates 5 data files from your session:
session.dbs: this binary database contains geometry, mesh and graphics-display information associated with the model.  It is the file you open when you reopen an existing session with the menu item file-open.
session.jou: this file contains  a sequential list of geometry, mesh, zone and tools commands executed during the session.
session.trn: this file contains the messages displayed in the Gambit Transcript window during the session.
session.lok: it is made in order to lock out the process number for the current Gambit session. Don't worry about this file...
session.grd: this file is created when you work with Fluent as the choosen solver. It is the file exported and the one you will open on Fluent.
Be carreful: you "export" the session from Gambit, but it seems that you should not "import" it on Fluent (it will find errors on your mesh whereas it is correct). Once Fluent is opened, it is preferable to use the read-case&data item.

Finding errors

            When you open your mesh with Fluent, it is possible that you made some mistakes in the entry of the geometry and/or the mesh Fluent will indicate that there is some errors. In order to correct them, reopen Gambit, then go on the menu item edit-runjournal, select the file session.jou, click on Edit/Run and Accept. You will obtain the journal of the session. Then you can do again all the operations step by step (you select them and click on step) and control  in the transcript window (left corner) the messages in order to find the message error.