mmr/vigrade-aeromap
Archived
1
0
Fork 0
Code Activity

added model type on aer_standard_CV.aer

Browse Source
This commit is contained in:
Erick
2021-11-30 23:40:14 +01:00
parent d74d00cc04
commit bf83c34a0e
3 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitignore
+1 -1
View File
@@ -1,3 +1,3 @@
notes
/pdftotext /pdftotext
/__pycache__ /__pycache__
notes
README.md
+2
View File
@@ -14,6 +14,7 @@ The Standard AER file contains aero maps as functions of front and rear ride hei
The maps resolution and extension is customizable, but it is strongly recommended that the maps are defined for The maps resolution and extension is customizable, but it is strongly recommended that the maps are defined for
all the ride heights combination allowed by the ride height saturation boundaries. Standard and user defined units could be used to define the maps. all the ride heights combination allowed by the ride height saturation boundaries. Standard and user defined units could be used to define the maps.
NOTE: the user-defined unit tags are not supported within tables. They are accepted for single value parameters only. NOTE: the user-defined unit tags are not supported within tables. They are accepted for single value parameters only.
## AER Advanced ## AER Advanced
@@ -27,6 +28,7 @@ The Advanced AER file contains:
- pitch torque - pitch torque
The maps resolution and extension is customizable, but it is strongly recommended that the maps are defined for all the ride heights combination allowed by the ride height saturation boundaries. Standard and user defined units could be used to define the maps. The maps resolution and extension is customizable, but it is strongly recommended that the maps are defined for all the ride heights combination allowed by the ride height saturation boundaries. Standard and user defined units could be used to define the maps.
NOTE: the user-defined unit tags are not supported within tables. They are accepted for single value parameters only. NOTE: the user-defined unit tags are not supported within tables. They are accepted for single value parameters only.
ATTENTION: the 1.0 file format is now deprecated, you need to use the 2.0 version or convert your 1.0 file to 2.0 file ATTENTION: the 1.0 file format is now deprecated, you need to use the 2.0 version or convert your 1.0 file to 2.0 file
aer_standard_CV.aer
+3
View File
@@ -17,6 +17,9 @@ $----------------------------------------------------------------units
{unit_type length force angle mass time conversion} {unit_type length force angle mass time conversion}
'm_s' 1 0 0 0 -1 1000.0 'm_s' 1 0 0 0 -1 1000.0
'kgpm3' -3 0 0 1 0 1e-9 'kgpm3' -3 0 0 1 0 1e-9
$-------------------------------------------------------------------------MODEL
[MODEL]
PROPERTY_FILE_FORMAT = 'STANDARD'
$-------------------------------------------------------------test_conditions $-------------------------------------------------------------test_conditions
[TEST_CONDITIONS] [TEST_CONDITIONS]
reference_velocity <kmh> = 100.0 reference_velocity <kmh> = 100.0