Which data can be processed?
- field data (cell- or point-based) from simulation or experiment
- Parameterized problem, i.e. a specific parameter combination can be assigned to each snapshot
- Topologically equivalent networks, i.e. the networks on which the field data are available all have the same number of points and possess the identical connectivity – if necessary, this must be established as part of preprocessing (link à navROM, navConvert, navMap)
What file formats are supported?
- Surfaces (.obj, .stl)
- VTK (.vtk, .vtp, .vtm)
- EnSight (.case)
- Femzip (.femzip) – requires license for Femzip*, which is not included in navROM.
What are the technical requirements?
- navROM is a command line application for a Linux operating system.
- Since for a lossless ROM calculation all input data must be loaded into the working memory at the same time, its size in everyday life usually limits the number of grid cells and variables that are available in ROM at the same time. You can estimate the memory requirement in bytes (exclusively for the ROM calculation) as follows: 4 / 8 bytes * K * N * (S + 3*V), where K corresponds to the number of snapshots, N to the number of grid cells, S to the number of scalar variables and V to the number of vector variables. Thus, a ROM with double precision (8 bytes), 100 snapshots, 2,000,000 grid cells, 3 scalar variables and one vector variable requires at least 9 GB for the calculation.