Graphical interface description ==================================== The graphical interface (IHM) is divided into 4 parts: 1. A menu bar 2. The tabs 3. Submission parameters 4. The status bar 5. Aster argument area 5. 2. 1. 4. 3. .. image:: images/10000000000003A20000025DA447ECE6A9F50359.png :width: 6.889in :height: 3.8744in .. _RefImage_10000000000003A20000025DA447ECE6A9F50359.png: Figure 2-1: Main window Tabs TESTS, SURCHARGE, and AGLA are now inactive. Menu bar ------------- The "Help" menu also provides access to menu descriptions. .. _Ref47944562: File menu ~~~~~~~~~~~~ .. image:: images/10000000000001730000011D9DBA3B409640EEF0.png :width: 3.0752in :height: 2.3626in .. _RefImage_10000000000001730000011D9DBA3B409640EEF0.png: Figure 2.1.1-1: File menu * **New**: Allows you to create a new profile. * **Open**: Open a profile created previously by astk. * **Save**: Save the current profile (this is done automatically when starting a calculation). * **Save as**: Save the current profile by giving the choice of the name of the profile and its location. * **Copyunder**: Copy the current profile to another directory and offers to copy the files (in data and/or results) that it references. * **Import**: *.export astk: Read an.export file from a previous run (this can be the file\*.p NNN from the $ HOME /flasher directory). *.export astk (add mode): unlike the classic import which starts from an empty profile, the files and directories found in the.export file are added to the current profile. Parameters and arguments are ignored. For example, this makes it possible to import a study into an overload profile. *.export of a form REX: Import the files attached to a file from REX whose number is given. * test case: Imports the files required to launch a test case. The files are taken from the selected execution machine. * test case (add mode): same + the files are added to those already present in the profile (including the overload). * **Export as**: Allows you to produce the current profile.export file. * **Close**: Close the current profile * **Exit**: End the application * The N most recently opened profiles are directly accessible from the File menu. .. _RefHeading__37401815: .. _Ref47944481: .. _Ref47944388: .. _Ref47942546: Setup menu ~~~~~~~~~~~~~~~~~~~~ .. image:: images/1000000000000135000000938AC6AB0844E19D9B.png :width: 2.8744in :height: 1.3673in .. _RefImage_1000000000000135000000938AC6AB0844E19D9B.png: Figure 2.1.2-1: Setup menu * **Servers**: Allows you to modify the configuration of the servers: calculation servers or file servers (see). For the computing servers, we choose the mode of downloading the *Aster* configuration: the server returns the list of available versions, the execution mode (batch and/or interactive) and the associated limits. You must specify the 'login' to use to connect to the server, and the directory where *Code_Aster* is installed. For file servers, choose "none" as the mode for downloading the Aster configuration. * **Preferences**: Set user preferences: **General* (See) For astk: Name, first name, email will be used for the link to the feedback management tool (issuance, consultation of anomaly and evolution sheets, etc.). The path to the editor and the terminal (xterm window) on the local machine, the version to be selected by default, the number of persistent profiles in the File menu, the message level (debug). You can choose to show all known file types, a restricted list, or a personal choice, sorted or not by name (see § :ref:`2.2.1 `). For job tracking: The number of rows displayed when consulting a running calculation (tail), and the automatic refresh rate in minutes. **Networks* (See) The network domain name of the machine and if the DHCP/VPN mode (dynamic IP address) is active, possibilities to set the variable DISPLAY for displaying external applications, the communication protocols used for shell commands (rsh or ssh) and file copying (rcp, scp or rsync). If you only work locally or if all the machines are in the same network domain, you can leave the domain name empty and ignore the warning at startup. *Warning*: use option DISPLAY wisely and only if the default value is not appropriate. Leave the field empty to let astk determine the DISPLAY alone (based on its value when launching astk, the domain name...). * **Colors**: Classic, KDE3 Crystal, Nostalgic, Personalized,... * **Policies** * **Save** the position and size of the windows .. image:: images/1000000000000343000002B270C07B5A5B189D90.png :width: 5.3319in :height: 4.4055in .. _RefImage_1000000000000343000002B270C07B5A5B189D90.png: Figure 2.1.2-2: Configuration/Servers Menu .. image:: images/10000000000002120000025DA443C90C05F6FA59.png :width: 3.7953in :height: 4.3307in .. _RefImage_10000000000002120000025DA443C90C05F6FA59.png: Figure 2.1.2-3: Configuration/Preferences/General Menu .. image:: images/1000000000000213000000FBC681567473DEA62C.png :width: 3.9366in :height: 1.8583in .. _RefImage_1000000000000213000000FBC681567473DEA62C.png: Figure 2.1.2-4: Configuration/Preferences/Network Menu **Remarks** Whether you choose the rsh/rcp or ssh/scp protocol, connections must work without a password: correctly filled .rhosts files or valid SSH private/public keys. Depending on what the "uname" command returns on the machine, astk sometimes thinks that it is on a remote machine and then does an rsh or ssh to execute a local command... In this case, the trivial connection from the machine to itself should also be configured. .. _Ref47944530: .. _Ref47944427: Tools menu ~~~~~~~~~~~ .. image:: images/1000000000000125000000EF88594DD8E89FF71D.png :width: 2.7181in :height: 2.2165in .. _RefImage_1000000000000125000000EF88594DD8E89FF71D.png: Figure 2.1.3-1: Tools menu * **Settings**: Allows you to configure the launch of the tools. Some tools are provided as standard (without necessarily being available on the local machine): * Post-processing with Code_Aster: Post-processing tool, command STANLEY, * Mesh converter: Allows you to convert a mesh from one format to another, the available formats are: aster, med, gmsh, ideas and gibi, * Convert to HDF format: Allows you to convert a classic Aster base to HDF format, * bsf: Multi-machine file explorer, *Eficas:*Aster* command file editor, *Gibi: Mesher and post-processing tool (usable for free with*Aster*), * Gmsh: Mesher and post-processing tool (free), * grace: 2D curve plotter. When you choose to launch Stanley, astk searches the profile for available databases (in order of preference for a result database, if there is none, a bhdf (base HDF) as a result, otherwise a database and finally, a data bhdf), produces a temporary profile from the current profile), produces a temporary profile from the current profile with an Aster command file that starts with POURSUITE () and starts STANLEY (). The user can add their own tools, configure the path to the tools (including modify the access command for the standard tools), define what types of files to associate the tool with, and specify whether the tool can be used on a remote file. The following codes can be used on the command line: * @F: absolute path of the selected file, * @R: directory containing the selected file, * @f: name of the file (without the directory), * @D: address of DISPLAY (the one known when the interface was launched). The tools are called either from the Tools menu, or from the context menu on a file in a list or in the Explorer (right button). To select a file, simply click on its name in a list (in the Study, Tests or Overload tab). By double-clicking on a file, the association between the file type and the tool to be used is based on the file name extension for bsf, while the type selected by the dropdown list (see tab descriptions) prevails in astk. .. _RefHeading__33273513: .. _Ref47944463: Menu Options ~~~~~~~~~~~~ * .. image: images/10000000000000 BC00000209443979972FDA1EEF .png :width: 1,7283 in :height: 4.7902 in .. _refImage_10000000000000 BC00000209443979972FDA1EEF .png: Figure 2.1.4-1: Options menu Arguments: Allows you to set optional arguments that will be passed on the command line when *Code_Aster* is executed. dbgjeveux: activates a mode different from the management of objects in memory to detect the overwriting and destruction of objects, rep_tools: defines the directory where the tools called from *Aster* are searched (onmetis or gibi for example), rep_dex: defines the directory where the external data (mesh data) are searched for, rep_mat: defines the directory where material catalog data is stored. ORBInitRef: allows you to contact an active Salome session (this value is automatically set when astk is launched from Salome). The selected arguments appear in the gray area of the arguments passed to*Code_Aster*. The left part of this zone is free. * Settings This involves defining optional parameters that will be written in the.export file. The first three are used when launching tests. nbmaxnook: maximum number of invalid test cases (NOOK, ARRET_ANORMAL...) before the test list is interrupted, cpresok: allows you to choose which tests you keep the result files for, RESOK: we keep the OK and NOOK test files, RESNOOK: we only keep the NOOK test files, facmtps: multiplying factor of test time (compared to the para reference time). Useful, for example, when submitting tests with an executable built in debug mode, which is slower. corefilesize: core file size limit during a crash * Launch options ncpus: define the number of processors used by the solver MULT_FRONT mpi_nbCPU: set the number of processors for parallelism MPI mpi_nbnode: define the number of nodes for parallelism MPI (Where the mpi_nbcpuprocessors will be distributed) class: allows you to choose the batch class (or class group) in which the calculation will be submitted. It is obviously necessary to check that the class exists and that the time and memory parameters are compatible with this class. Departure: allows you to postpone the start of a calculation. The departure time is provided in hour:minute format (to specify the departure day, the syntax depends on the work manager). distrib: start a parametric study (value yes/no, see § :ref:`6 `). exectool: launch using a particular tool (see § :ref:`5.6.1 `) multiple: runs the profile on several machines (yes/no value, see § :ref:`7 `). Help menu ~~~~~~~~ .. image:: images/1000000000000167000000DB6E18D6570F0C356A.png :width: 2.822in :height: 1.7209in .. _RefImage_1000000000000167000000DB6E18D6570F0C356A.png: Figure 2.1.5-1: Help menu * Introduction/Calculation settings/Menus: access to the help text *Calculation parameters: allows you to define the memory size, the version of*Code_Aster* that will be used, the calculation mode (Batch or interactive),... * File/Setup/Tools/Options menus... * History of modifications: Evolution of astk over the versions, new possibilities, corrections made, known anomalies... * Technical Assistance... * Common problems: Some frequently asked questions with their solutions. * Message window: Information messages , error messages are written in this window. With a message level greater than or equal to 1 (see [§ :ref:`2.1.2 `]), more or less information is obtained. * About...: the essential information window. The tabs ----------- There are five buttons in this area. We talk about a tab when the content under the button changes according to who is pressed. Graphically, these are not "real" tabs because the widget does not exist in the standard Tk library (and we did not want to add an additional prerequisite!). ETUDE is a tab in which you fill in the list of files needed to launch a study. REX is a simple button that displays a list of choices. The other buttons are now deactivated. .. _RefHeading__5643_2079996570: .. _Ref47944591: .. _Ref47944504: .. _Ref47943270: .. _Ref47943250: Tab ETUDE ~~~~~~~~~~~~ To access files more easily, browse trees more quickly (files are often grouped in nearby directories), or even simplify the display of file names, you can define a **base path**. .. image:: images/100002010000021B00000018736C0680B3C77CB2.png :width: 5.6138in :height: 0.2492in .. _RefImage_100002010000021B00000018736C0680B3C77CB2.png: Figure 2.2.1-1: Base path It is defined by clicking on the Browse button .. image:: images/100000000000001B00000018E0154DDD57B9DD24.png :width: 0.2252in :height: 0.2in .. _RefImage_100000000000001B00000018E0154DDD57B9DD24.png: and we choose the directory that will be the directory by default. Each tab contains a list of files (two lists for SURCHARGE). .. image:: images/10000000000001F10000004576D7D209E6B31692.png :width: 5.1772in :height: 0.7189in .. _RefImage_10000000000001F10000004576D7D209E6B31692.png: Figure 2.2.1-2: List of files and directories One file or directory is defined per line. From left to right, we find: * Type: type of file or directory; * Server: name of the server where the file/directory is located; * Name: path to the file: absolute if it starts with '/', relative to the base path if not; * UL: logical unit number associated with this file; * D, R, C: check boxes to indicate if the file/directory is respectively in data, result, compressed (with gzip). When changing the type of a file/directory, values by default are set for the D, R, C indicators and the logical unit number. **Note on types:** *Code_Aster manipulates files via Fortran procedures that use logical unit numbers (file* *fort.19 for example); it therefore assigns logical unit numbers by default to simplify the user's life. The "type" thus allows easy access to the numbers used by default; it also allows astk to verify that the user provides consistent data (for example, that a directory for such a type is provided).* To handle the list, we have six buttons: * .. image:: images/10000000000000170000170000001b34383f7b49a2 DD5F .png :width: 0.2327 in :height: 0.2728 in .. _refImage_10000000000000170000001b34383f7b49a2 DD5F .png: : add a new blank entry at the end of the list; * .. image: images/10000000000000180000001705599 DF81D7E281C .png :width: 0.2161 in :height: 0.2071 in .. _refImage_10000000000000180000001705599 DF81D7E281C .png: : add a file/directory to the end of the list by browsing the file tree; * .. image: images/10000000000000180000001 AEF283A96A6D967EA .png :width: 0.25 in :height: 0.2709 in .. _refImage_10000000000000180000001 AEF283A96A6D967EA .png: : Deletes the row currently selected from the list. A right click allows you to delete all the lines; * .. image:: images/10000000000000150000001b72c3d3e45 ED4D554 .png :width: 0.25 in :height: 0.3209 in .. _refImage_10000000000000150000001b72c3d3e45 ED4D554 .png: : open the file/directory currently selected in the list with the editor of the server where the file is located (cf. [§ :ref:`4.1 `]). If it is a directory, all the files in the directory are opened with the editor (watch out for directories containing a lot of files or binary files that cannot be edited!) ; * .. image:: images/100000000000001A0000001350B22C414D1F0F63.png :width: 0.2835 in :height: 0.2063 in .. _RefImage_100000000000001A0000001350B22C414D1F0F63.png: : move one line up; * .. image:: images/100000000000001a000000122684c1285e92 DA0D .png :width: 0.3008 in :height: 0.2083 in .. _refImage_100000000000001a000000122684c1285e92 DA0D .png: : Move one line down. **Arguments**: This text box allows you to pass arguments to the *Aster* executable. See also [:ref:`§2.1.4 <§2.1.4>`]. For example, you can start the calculation interactively and ask that the command prompt be proposed at the end of the instructions to continue the execution of commands manually with the "--interact" option. **Context menu:** By right-clicking on an entry in the list, you access a context menu: * Open: launch the tool associated with this type of file (determined by the "Type" field, and not the file extension), if no tool is associated with this type, we edit the file; * Edit: edit the file (or all files in the directory) in the same way as the button .. image:: images/10000000000000150000001b72c3d3e45 ED4D554 .png :width: 0.25 in :height: 0.3209 in .. _refImage_10000000000000150000001b72c3d3e45 ED4D554 .png0: ; * Open with...: you can choose to open the selected file with one of the available tools (the result can be surprising if the tool does not know this type of file!) ; * Default values: the interface determines a default file name according to the "Type" chosen from the profile name (.astk file), no value is proposed if the profile has not yet been saved (is generally used on a blank line that has just been inserted, the D/R/C indicators are not affected by this operation); * Terminal: allows you to open an xterm terminal window * Properties: shows file permissions, size, date, and time (ls-la command). List of types for ETUDE ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. csv-table:: "comm:", "*Aster* command files (including tracking files)" "mail:", "mesh file in *Aster* format" "error:", "error file (Strt.9 from Aster)" "mess:", "runtime message file" "resu:", "result file (test printing, printing in*Aster* format)" "base:", "directory containing the base of the calculation" "bhdf", "directory containing the calculation base in HDF format" "cast:", "result file in CASTEM format" "mast:", "kept for compatibility reasons" "mgib:", "mesh in Gibi format" "mmed:", "mesh in MED format" "msh:", "mesh in Gmsh format" "msup:", "mesh in IDEAS format" "datg:", "Gibi command file" "pos:", "result file in Gmsh format" "ensi:", "result directory in Ensight format" "dat:", "result file containing curves in XMGRACE format" "ps:", "postscript file" "agraf:", "result file containing the data for Agraf (the old versions of Aster wrote the directives and the data in the same file that had to be split with the post_agra command on the reference machine)" "digr:", "result file containing the directives for Agraf" "rmed:", "result file in MED format" "unv:", "result file in the format "UNiVersel" (IDEAS)" "distr:", "file of values used for a parametric study" "hostfile:", "file describing the machine resources to be used (parametric study)" "name:", "to retrieve from its name, a file found in the temporary directory /tmp" "para:", "parameter file (transcription of the calculation parameters for the tests)" "repe:", "data and/or results directory (allows to transmit/retrieve the complete content of a directory; as one does not assign logical unit numbers *Aster* must access files by name). directory of results during a parametric study" "libr:", "file or directory at the user's choice" "bc:", "launch script generated by the service (so you can retrieve it, modify it...)." During an astout on the reference machine, resu_test must be on the reference machine. During a parametric study, the results directory (repe type) must be on the execution machine. .. _Ref47943491: .. _Ref47943476: .. _Ref47943459: REX button ~~~~~~~~~~ This button allows: *D'**Issue a form without attaching the profile**: This function allows the user to issue a feedback sheet to report an anomaly in*Code_Aster*(AL: software anomaly), request an evolution of*Code_Aster*(EL: software evolution) (EL: software evolution), in one of the associated tools (Metis, Lobster, Eficas, astk, bsf...) (AO: tool anomaly) (EL: software evolution), in one of the associated tools (Metis, Lobster, Eficas, astk, bsf...) (AO: tool anomaly), a modification of the documentation (ED: documentation evolution), or a request for modeling expertise (AOM: assistance in optimizing modeling) ). Information relating to the issuer of the form is accessible through the*Configuration/Interface*menu. The files in the current profile are not attached to the form, which can make it very difficult to process the form. It is recommended to use "issue a form and associate the files". The version of*Code_Aster*indicated is the one selected in the interface (*Calculation parameters*). *To**Issue a form and associate the files**: This function allows you to issue the same type of form as the previous one, this time the data included in the profile is attached to the form. For an anomaly, files to reproduce the error should always be provided. This does not prevent the user from trying to isolate the problem encountered as much as possible, in particular trying to attach a study on a model that requires little memory and calculation time! *To** Consult the sheets **: allows access to the feedback management tool (on the reference machine). **Note** *Features REX are only available on the reference server.* .. image:: images/10000000000002A400000265A594A394AD2C532B.png :width: 4.7244in :height: 4.7244in .. _RefImage_10000000000002A400000265A594A394AD2C532B.png: Figure 2.2.2-1: Issuance of an anomaly sheet .. _Ref47944608: .. _Ref47943507: Submission settings ------------------------ The calculation parameters are provided on the right side of the main window. .. image:: images/10000000000000E100000140CE9A4FD42088626E.png :width: 2.0874in :height: 2.5689in .. _RefImage_10000000000000E100000140CE9A4FD42088626E.png: Figure 2.3-1: Calculation parameter areas We define the quantity of: * Total memory used for the job (in megabytes). * the maximum calculation time (in seconds, minutes: seconds or hour: minutes: seconds). You choose on which machine the calculation is executed, the version of *Code_Aster* used, whether the calculation is submitted in batch or interactively. The "interactive tracking" option allows you to execute the calculation while following its execution in a terminal-type window. If the calculation is started on a remote server, this terminal is executed remotely. This is why the interface is then blocked until the execution of the calculation is complete to keep the ssh connection open. debug/nodebug: for a study without overloading, you specify which executable you want to use (provided that both are available). The "Launch" button executes actions according to the checked tabs. The "Job Tracking" button opens the window described below. **Mode of operation** (for a ETUDE): When launching a study, an option button is available next to the "Start" button. Three launch modes are available: * "run": executes the study (classic operation), * "dbg": start the study using the debugger, * "pre": prepare the working directory without running the study. When you select "dbg" or "pre", the "debug" mode is chosen by default. .. _Ref94334786: Status bar ------------ The text box at the bottom of the main window provides help when navigating through the menus, or when the pointer passes over the interface buttons. When a calculation is started, the operations in progress are shown here. .. image:: images/10000000000002FE00000023447EE6FC067DC368.png :width: 6.889in :height: 0.3138in .. _RefImage_10000000000002FE00000023447EE6FC067DC368.png: Figure 2.4-1: Status bar Job tracking -------------- This window provides information on the status of the calculations started, which is displayed in the form of a list. By right-clicking on a calculation, you have the following choices: * **Edit** is divided into "Output file", "Error file" and "Export files" which gives access to the messages sent by the job on standard output (stdout) and error output (stderr). You can also access the.export file used during execution. A double-click on a job in the list also displays the output file. These files are first copied locally into a temporary directory and then opened with the local editor. * **Download the result files** forces the results files to be copied. This action is done automatically when the calculation changes to state ENDED. If this step failed (network problem), it would allow it to be run again. * **Refresh** queries the servers on which calculations are in progress. The check box allows you to update automatically at a frequency defined in *Configuration/Interface*. * **Refresh all** refreshes the status of all calculations that have not been completed. * **Delete** deletes the jobs selected from the list, the files linked to this job in the flasher and stops the calculation if this one is not finished (by sending signal SIGKILL). * **Stopping cleanly** sends signal SIGUSR1 to the calculation. *Code_Aster* intercepts this signal to interrupt the calculation, then properly closes the database that will be retrieved (if a database is a result in the profile). * **Purge flasher** searches all servers and deletes files in the flasher directory that are not accessible from the job tracker. * **Search** allows you to consult the last lines of the message file of a job *during running* (it does nothing on a completed job). You can use the "Filter" text box to display only lines containing the specified character string (in regular expression form). The text box allows you to follow the progress of requests executed on remote servers. Each row corresponds to a job, there are 13 columns: * Job number (batch), interactive process number * The name of the job (name of the profile for a study, an overload, or name of the function AGLA) * Submission date * Submission time * Job status (PEND, RUN, SUSPENDED, ENDED) * Job diagnosis (OK, NOOK, _ ALARM, _, _, _ ABNORMAL...) ERROR * Batch or "interactive" queue name *Time CPU of run*Aster* * Login to the calculation server used * Address of the computing server used * Computing machine (name of the node for a cluster) * ASTK version * Batch/interactive indicator .. _Ref94335787: