Searched refs:variables (Results 1 – 15 of 15) sorted by relevance
| /libCEED/examples/fluids/ |
| H A D | pytorch_pkgconfig.py | 12 variables = {} variable 24 variables['prefix'] = Path(C.library_paths()[0]).parent.as_posix() 57 variables['torch_cuda_path'] = torch_cuda_path.as_posix() 63 for variable, value in variables.items():
|
| H A D | README.md | 8 The state variables are mass density, momentum density, and energy density. 613 …- State variables to solve solution with. `conservative` ($\rho, \rho \bm{u}, \rho e$), `primitive…
|
| H A D | index.md | 42 for the state variables 5-dimensional vector 664 …i(\bm{x},t)$, and potential temperature, $\theta(\bm{x},t)$, that relate to the state variables via 839 `sclr_2` are reserved for turbulence modeling variables. They are not used in
|
| /libCEED/examples/ceed/ |
| H A D | ex1-volume-f.h | 42 ! u is solution variables with shape [1, Q] 46 ! v is solution variables with shape [1, Q]
|
| /libCEED/julia/LibCEED.jl/src/ |
| H A D | C.jl | 23 # some global variables
|
| /libCEED/benchmarks/ |
| H A D | README.md | 28 variables can be set on the command line:
|
| /libCEED/doc/sphinx/source/ |
| H A D | libCEEDdev.md | 217 1. All local variables of a particular type (for example, `CeedInt`) should be listed on the same l… 228 2. Local variables should be initialized in their declaration when possible. 233 6. In libCEED functions, variables must be declared at the beginning of the code block (C90 style),… 234 …However, when variables are only used in a limited scope, it is encouraged to declare them in that…
|
| H A D | libCEEDapi.md | 212 - **L-**, **E-** and **Q-vector** are represented as variables of type {ref}`CeedVector`. 248 These functions are turned into the {ref}`CeedQFunction` variables `qf_setup` and `qf_mass` in the …
|
| H A D | releasenotes.md | 119 - Support for primitive variables for more accurate boundary layers and all-speed flow.
|
| /libCEED/examples/ |
| H A D | README.md | 91 To build the examples, set the `DEAL_II_DIR`, `MFEM_DIR`, `PETSC_DIR`, and `NEK5K_DIR` variables an…
|
| /libCEED/ |
| H A D | README.md | 88 which stores these variables in `config.mk`. 237 …, set the `MFEM_DIR`, `PETSC_DIR` (and optionally `PETSC_ARCH`), and `NEK5K_DIR` variables and run: 370 The usual variables like `CC` and `CFLAGS` are used, and optimization flags for all languages can b…
|
| H A D | Doxyfile | 22 # configuration file without replacing the environment variables or CMake type 23 # replacement variables: 749 # appearance of the value of individual variables and macros / defines can be 2100 # Set optional variables used in the generation of an RTF document. Syntax is 2245 # The names of the make variables in the generated doxyrules.make file are 2248 # overwrite each other's variables. 2464 # dependencies (inheritance, containment, and class references variables) of the
|
| H A D | Makefile | 226 MFLAGS := -j $(NPROCS) --warn-undefined-variables \
|
| /libCEED/examples/solids/ |
| H A D | index.md | 65 In their most general form, constitutive models define $\bm \sigma$ in terms of state variables. 66 In the model taken into consideration in the present mini-app, the state variables are constituted …
|
| /libCEED/rust/libceed-sys/c-src/ |
| H A D | Makefile | 226 MFLAGS := -j $(NPROCS) --warn-undefined-variables \
|