add autoloads
This commit is contained in:
304
lisp/apdl-mode/apdl-mode-autoloads.el
Normal file
304
lisp/apdl-mode/apdl-mode-autoloads.el
Normal file
@@ -0,0 +1,304 @@
|
||||
;;; apdl-mode-autoloads.el --- automatically extracted autoloads (do not edit) -*- lexical-binding: t -*-
|
||||
;; Generated by the `loaddefs-generate' function.
|
||||
|
||||
;; This file is part of GNU Emacs.
|
||||
|
||||
;;; Code:
|
||||
|
||||
(add-to-list 'load-path (or (and load-file-name (directory-file-name (file-name-directory load-file-name))) (car load-path)))
|
||||
|
||||
|
||||
|
||||
;;; Generated autoloads from apdl-initialise.el
|
||||
|
||||
(autoload 'apdl-initialise "apdl-initialise" "\
|
||||
Initialise the customisation variables.
|
||||
When argument FORCE is non-nil overwrite some of the already set
|
||||
customisation variables.
|
||||
|
||||
(fn &optional FORCE)")
|
||||
(register-definition-prefixes "apdl-initialise" '("apdl-"))
|
||||
|
||||
|
||||
;;; Generated autoloads from apdl-keyword.el
|
||||
|
||||
(register-definition-prefixes "apdl-keyword" '("apdl-"))
|
||||
|
||||
|
||||
;;; Generated autoloads from apdl-mode.el
|
||||
|
||||
(add-to-list 'auto-mode-alist '("\\.mac\\'" . apdl-mode))
|
||||
(add-to-list 'auto-mode-alist '("\\.ans\\'" . apdl-mode))
|
||||
(add-to-list 'auto-mode-alist '("\\.dat\\'" . apdl-mode))
|
||||
(add-to-list 'auto-mode-alist '("\\.inp\\'" . apdl-mode))
|
||||
(autoload 'apdl-mode "apdl-mode" "\
|
||||
Editor support for the APDL language and working with Ansys MAPDL.
|
||||
|
||||
APDL-Mode (formerly Ansys-Mode) - in conjunction with the
|
||||
GNU-Emacs editor - is an advanced APDL environment with features
|
||||
like, pin-pointing the APDL reference documentation, keyword
|
||||
completion, code templates, dedicated highlighting, solver
|
||||
communication (GNU-Linux only), license reporting, etc. Over the
|
||||
years it has accumulated lots of features for writing WorkBench /
|
||||
Discovery AIM Command (APDL) objects and debugging complete FEA
|
||||
models in APDL code.
|
||||
|
||||
The extensive documentation can be accessed from the APDL-Mode
|
||||
menu or by calling the function `apdl-mode-help' with
|
||||
\\[apdl-mode-help].
|
||||
|
||||
\\{apdl-mode-map}" t)
|
||||
(autoload 'apdl "apdl-mode" "\
|
||||
Open a new buffer in APDL-Mode.
|
||||
You must save the buffer (connect it with a file-name), otherwise
|
||||
possible edits are lost." t)
|
||||
(autoload 'apdl-mode-version "apdl-mode" "\
|
||||
Display the APDL-Mode version numbering scheme.
|
||||
Together with the APDL-Mode update date and the Ansys version on
|
||||
which the keyword- and completion system is based upon." t)
|
||||
(register-definition-prefixes "apdl-mode" '("apdl-"))
|
||||
|
||||
|
||||
;;; Generated autoloads from apdl-process.el
|
||||
|
||||
(autoload 'apdl-start-classics "apdl-process" "\
|
||||
Start the Ansys MAPDL Classics graphical user interface.
|
||||
The output of the solver is captured in an Emacs buffer called
|
||||
*Classics* under GNU-Linux. Under Windows it is not possible to
|
||||
capture the output here, only the exit code. Please
|
||||
see `apdl-start-batch-run' for the documentation of these codes.
|
||||
|
||||
MAPDL command line options:
|
||||
-aas : implies -b
|
||||
-b : implies -i and -o
|
||||
|
||||
-lch : undocumented, command line built from the Ansys Launcher
|
||||
-t : undocumented, maximum solver time -t 10:30:00
|
||||
|
||||
V2020R2:
|
||||
|
||||
-aas : Enables server mode. When enabling server mode, a custom
|
||||
name for the keyfile can be specified using the -iorFile
|
||||
option. For more information, see Mechanical APDL as a Server
|
||||
User's Guide.
|
||||
|
||||
-acc device : Enables the use of GPU hardware to accelerate the
|
||||
analysis. See GPU Accelerator Capability in the Parallel
|
||||
Processing Guide for more information.
|
||||
|
||||
-amfg : Enables the additive manufacturing capability (requires
|
||||
an additive manufacturing license). For general information
|
||||
about this feature, see AM Process Simulation in Ansys
|
||||
Workbench.
|
||||
|
||||
-ansexe : In the Ansys Workbench environment, activates a custom
|
||||
Mechanical APDL executable.
|
||||
|
||||
-b list or nolist : Activates the Mechanical APDL program in
|
||||
batch mode. The options -b list or -b by itself cause the input
|
||||
listing to be included in the output. The -b nolist option
|
||||
causes the input listing not to be included. For more
|
||||
information about running Mechanical APDL in batch mode, see
|
||||
Batch Mode.
|
||||
|
||||
-custom : Calls a custom Mechanical APDL executable. See Running
|
||||
Your Custom Executable in the Programmer's Reference for more
|
||||
information.
|
||||
|
||||
-d device : Specifies the type of graphics device. This option
|
||||
applies only to interactive mode. For Linux systems, graphics
|
||||
device choices are X11, X11C, or 3D. For Windows systems,
|
||||
graphics device options are WIN32 or WIN32C, or 3D.
|
||||
|
||||
-db value : Defines the portion of workspace (memory) to be used
|
||||
as the initial allocation for the database. The default is 1024
|
||||
MB. Specify a negative number (-value) to force a fixed size
|
||||
throughout the run; useful on small memory systems.
|
||||
|
||||
-dir : Defines the initial working directory. Using the -dir
|
||||
option overrides the ANSYS212_WORKING_DIRECTORY environment
|
||||
variable.
|
||||
|
||||
-dis : Enables Distributed Ansys. See the Parallel Processing
|
||||
Guide for more information.
|
||||
|
||||
-dvt : Enables Ansys DesignXplorer advanced task (add-on).
|
||||
|
||||
-g : Launches the Mechanical APDL program with the Graphical User
|
||||
Interface (GUI) on. If you select this option, an X11 graphics
|
||||
device is assumed for Linux unless the -d option specifies a
|
||||
different device. This option is not used on Windows
|
||||
systems. To activate the GUI after Mechanical APDL has started,
|
||||
enter two commands in the input window: /SHOW to define the
|
||||
graphics device, and /MENU,ON to activate the GUI. The -g
|
||||
option is valid only for interactive mode. Note: If you start
|
||||
Mechanical APDL via the -g option, the program ignores any
|
||||
/SHOW command in the start.ans file and displays a splash
|
||||
screen briefly before opening the GUI windows.
|
||||
|
||||
-i inputname : Specifies the name of the file to read input into
|
||||
Mechanical APDL for batch processing. On Linux, the preferred
|
||||
method to indicate an input file is <.
|
||||
|
||||
-iorFile keyfile_name : Specifies the name of the server keyfile
|
||||
when enabling server mode. If this option is not supplied, the
|
||||
default name of the keyfile is aas_MapdlID.txt. For more
|
||||
information, see Mechanical APDL as a Server Keyfile in the
|
||||
Mechanical APDL as a Server User's Guide.
|
||||
|
||||
-j Jobname : Specifies the initial jobname, a name assigned to
|
||||
all files generated by the program for a specific model. If you
|
||||
omit the -j option, the jobname is assumed to be file.
|
||||
|
||||
-l language : Specifies a language file to use other than US
|
||||
English. This option is valid only if you have a translated
|
||||
message file in an appropriately named subdirectory in
|
||||
/ansys_inc/v212/ansys/docu (or Program Files\\ANSYS
|
||||
Inc\\V212\\ANSYS\\docu on Windows systems).
|
||||
|
||||
-m workspace : Specifies the total size of the workspace (memory)
|
||||
in megabytes used for the initial allocation. If you omit the
|
||||
-m option, the default is 2 GB (2048 MB). Specify a negative
|
||||
number (-value) to force a fixed size throughout the run.
|
||||
|
||||
-machines : Specifies the machines on which to run a Distributed
|
||||
Ansys analysis. See Starting Distributed Ansys in the Parallel
|
||||
Processing Guide for more information.
|
||||
|
||||
-mpi : Specifies the type of MPI to use. See the Parallel
|
||||
Processing Guide for more information.
|
||||
|
||||
-mpifile : Specifies an existing MPI file (appfile) to be used in
|
||||
a Distributed Ansys run. See Using MPI Files in the Parallel
|
||||
Processing Guide for more information.
|
||||
|
||||
-na : Specifies the number of GPU accelerator devices per machine
|
||||
or compute node when running with the GPU accelerator
|
||||
feature. See GPU Accelerator Capability in the Parallel
|
||||
Processing Guide for more information.
|
||||
|
||||
-name value : Defines Mechanical APDL parameters at program
|
||||
start-up. The parameter name must be at least two characters
|
||||
long. For details about parameters, see the Ansys Parametric
|
||||
Design Language Guide.
|
||||
|
||||
-np : Specifies the number of processors to use when running
|
||||
Distributed Ansys or Shared-memory Ansys. See the Parallel
|
||||
Processing Guide for more information.
|
||||
|
||||
-o outputname : Specifies the name of the file to store the
|
||||
output from a batch execution of Mechanical APDL. On Linux, the
|
||||
preferred method to indicate an output file is >.
|
||||
|
||||
-p productname : Defines which Ansys product will run during the
|
||||
session. For more detailed information about the -p option, see
|
||||
Selecting an Ansys Product via the Command Line.
|
||||
|
||||
-ppf license feature name : Specifies which HPC license to use
|
||||
during a parallel processing run. See HPC Licensing in the
|
||||
Parallel Processing Guide for more information.
|
||||
|
||||
-rcopy : On a Linux cluster, specifies the full path to the
|
||||
program used to perform remote copy of files. The default value
|
||||
is /usr/bin/scp.
|
||||
|
||||
-s read or noread : Specifies whether the program reads the
|
||||
start.ans file at start-up. If you omit the -s option,
|
||||
Mechanical APDL reads the start.ans file in interactive mode
|
||||
and not in batch mode.
|
||||
|
||||
-schost host name : Specifies the host machine on which the
|
||||
coupling service is running (to which the co-simulation
|
||||
participant/solver must connect) in a System Coupling analysis.
|
||||
|
||||
-scid value : Specifies the licensing ID of the System Coupling
|
||||
analysis.
|
||||
|
||||
-sclic port@host : Specifies the licensing port@host to use for
|
||||
the System Coupling analysis.
|
||||
|
||||
-scname name of the solver : Specifies the unique name used by
|
||||
the co-simulation participant to identify itself to the
|
||||
coupling service in a System Coupling analysis. For Linux
|
||||
systems, you need to quote the name to have the name recognized
|
||||
if it contains a space: ansys212 -scname \"Solution 1\"
|
||||
|
||||
-scport port number : Specifies the port on the host machine upon
|
||||
which the coupling service is listening for connections from
|
||||
co-simulation participants in a System Coupling analysis.
|
||||
|
||||
-smp : Enables shared-memory parallelism. See the Parallel
|
||||
Processing Guide for more information.
|
||||
|
||||
-usersh : Directs the MPI software (used by Distributed Ansys) to
|
||||
use the remote shell (rsh) protocol instead of the default
|
||||
secure shell (ssh) protocol. See Configuring Distributed Ansys
|
||||
in the Parallel Processing Guide for more information.
|
||||
|
||||
-v : Returns the Mechanical APDL release number, update number,
|
||||
copyright date, customer number, and license manager version
|
||||
number.
|
||||
" t)
|
||||
(autoload 'apdl-start-launcher "apdl-process" "\
|
||||
Start the Ansys Launcher." t)
|
||||
(autoload 'apdl-user-license-status "apdl-process" "\
|
||||
Display only licenses which are used by the user.
|
||||
Show the status for the user `apdl-username' in a separate buffer
|
||||
*User-Licenses*. The license type variable `apdl-license'
|
||||
determines a highlighting of the license server summary rows.
|
||||
There are additional keybindings for the license buffer
|
||||
*User-licenses*:
|
||||
|
||||
- `d' for a license description of all available features
|
||||
- `g' for updating the license status
|
||||
- `?' and `h' for showing this help,
|
||||
- `l' for the general license status and
|
||||
- `q' for burying the *User-licenses* buffer
|
||||
- `Q' for killing the Buffer" t)
|
||||
(autoload 'apdl-license-status "apdl-process" "\
|
||||
Display the lmutil license status.
|
||||
With the optional argument FEATURES non nil summarise all license
|
||||
features with the Ansys license feature description. Show the
|
||||
status and summary in a separate buffer, the license type
|
||||
variable `apdl-license' determines a highlighting of the license
|
||||
server summary rows. There are additional keybindings for the
|
||||
license buffer *APDL-licenses*:
|
||||
|
||||
- `g' updating the license status,
|
||||
- `d' updating the license status with feature descriptions
|
||||
- `o' for showing an occur buffer with the interesting licenses from
|
||||
`apdl-license-occur-regexp',
|
||||
- `u' for displaying all the user license,
|
||||
- `?' and `h' for showing this help,
|
||||
- `Q' for killing the Buffer and
|
||||
- `q' for burying it below another buffer.
|
||||
|
||||
(fn &optional FEATURES)" t)
|
||||
(autoload 'apdl-license "apdl-process" "\
|
||||
Change the Ansys license type.
|
||||
And store it in the variable `apdl-license'." t)
|
||||
(register-definition-prefixes "apdl-process" '("apdl-"))
|
||||
|
||||
|
||||
;;; Generated autoloads from apdl-template.el
|
||||
|
||||
(register-definition-prefixes "apdl-template" '("apdl"))
|
||||
|
||||
|
||||
;;; Generated autoloads from apdl-wb-template.el
|
||||
|
||||
(register-definition-prefixes "apdl-wb-template" '("apdl-"))
|
||||
|
||||
;;; End of scraped data
|
||||
|
||||
(provide 'apdl-mode-autoloads)
|
||||
|
||||
;; Local Variables:
|
||||
;; version-control: never
|
||||
;; no-byte-compile: t
|
||||
;; no-update-autoloads: t
|
||||
;; no-native-compile: t
|
||||
;; coding: utf-8-emacs-unix
|
||||
;; End:
|
||||
|
||||
;;; apdl-mode-autoloads.el ends here
|
||||
Reference in New Issue
Block a user