You could have at any point sent specific questions to Chris. But today was too late. Imagine everybody would have that question.Alonso Fan wrote:thanks
files have been uploaded, please can you check everything is there, just in case
if anything minor is wrong I can change it before the end of the day
Matteo, you are a funny man. I suggest this: Take the data your eyes can read and use it to calculate the CoP. When you are done compare it to the CoP reported by that post-processing tool that came with MantiumWFlow. If both results match, we know that there are no mistakes in the calculation.CAEdevice wrote:I was wondering wich way the CoP is computed this year (would it be possible to write it into the txt logs?).
To have an esitimation, I use the Cl.A front and rear values and the Cd.A (all converted in N), guessing the vertical position of the resultant drag (I use 0,5m).
Looks like all the required parts were submitted and the scale is correct. The compliance checks will start once the deadline has passed.Alonso Fan wrote:thanks
files have been uploaded, please can you check everything is there, just in case
if anything minor is wrong I can change it before the end of the day
cdsavage wrote:Looks like all the required parts were submitted and the scale is correct. The compliance checks will start once the deadline has passed.Alonso Fan wrote:thanks
files have been uploaded, please can you check everything is there, just in case
if anything minor is wrong I can change it before the end of the day
I will show you tomorrow. Sorry for making so much fun about your reading abilities. If we manage to have something like a MVRC users meeting I will invite you to as many beer as you like.CAEdevice wrote:I am glad I make you smile.
What I actually asked is: wich algorithm do you use to compute CoP?
Solidworks exports the files in *.STL format. With KVRC I had to change the extension to *.stl for it to recognise the files. In this instance I changed the file extensions to *.stl and OF now starts a calculation.LVDH wrote:I forgot, it is odd that Paraview cannot open your stl files. Other software opens them. Maybe you are using some odd format, strangely there seem to be many stl formats.
And I noticed something else super strange. Your stl files end with *.STL, try changing it to *.stl. If it works then we have another "bug" I have to fix in MantiumWFlow.
I will send a log file tonight. I managed to start a calculation after changing the file extension from *.STL to *.stl. But now the meshing and smoothing iterations stop at my "HX_rhs" part. I don't understand the error, so I will send the log file and the the *.stl file.LVDH wrote:It is probably a bit late to get this solved properly, but make sure to use ascii stl files (your uploaded files seem fine), make sure that MantiumWFlow does not show any warning or error messages and have a look at a line that should look something like this:TalnoRacing wrote:Yes I checked again. This is the result in the solver file:
Coefficients
Cm : 0 (pressure: 0 viscous: 0)
Cd : 0 (pressure: 0 viscous: 0)
Cl : 0 (pressure: 0 viscous: 0)
Cl(f) : 0
Cl(r) : 0
I get this for each time interval.These are the Xmin, Xmax,Ymin, Ymax, Zmin and Zmax values of your car. If you have scaled them incorrectly then the force measurements will not work as the car is either far too small or way to big. The next release of MantiumWFlow will show a warning for this.Code: Select all
('max BB dimensions: ', [-0.999986012615143, 4.00000000000001, -1.00596606731415, 1.00596606731415, -0.0500000007450581, 0.965000000000001])
Close to the end of all the MantiumWFlow text you should find something like this:If not, you are doing something wrong. You can send me an email with the output, but it is late and I had some beer already so you might have to wait until tomorrow morning.Code: Select all
('writting case: ', '.../MVRC/Monaco_2016/.../..._Race01_20160902') ... and done.