body
wing-front
wing-rear
cooling-intake
cooling-exhaust
engine-intake
engine-exhaust
hx-front
hx-rear
parts-offset.txt
If this is for the fallback option 2B, best to use inlet-cooling in place of hx-front and inlet-exhaust in place of hx-rear.
I have the impression that Opt1 will be a little more convenient if the Opt2/B inlets areas will be constrained. In my opinion (but we could wait after the pre season race results) the Opt2/B inlets/outlets surfaces would be free or with a lower minimum area (40000mm2?), but with the same pressure×area differential.
The minimum areas are really there to make sure that our constraints parameters are not leading to tiny sidepods. For option 2/B we reduced the pressure force to account for the modelled pressure loss at the air intake/exhaust in the cooling ducts.
Julien can confirm, but I believe that for the first round at least, we will need to use the fallback method for the entries using K4.1 option 2.
Confirmed. I have still to get through to get the porosity parameters finalised.
Hi, could you confirm that, if I run an Opt2/B with OCCFD, naming the heat exchangers surfaces as "cooling_inlet" and"cooling_outlet", I'm simulating the same official bc that will be applied during a race with Opt2/B?
Confirmed. Essentially the boundary conditions are the same. It is only the extract threshold that changes due to the modelled losses at the intake/exhaust and within the ducts themselves.
Has the OCCFD 'test' setting been changed? I ran it in AWS and it was still running over 24hrs later so terminated it. Previously it was over and done with in minutes.
No, it should not have happen. The simulation should be over in minutes. I will check and report. Also I haven't had time to look into the cheaper option - it should be a little cheaper, but not massively. The computational time should be similar to the one for last year.
You could also try to import the stl into sketchup and to translate it into the right place.
Importing STL into sketchup can take a long time (all night in some cases). Personally I like ParaView to check the min and maximum limits of the STL. But ParaView is painful to translate the STL, and I would use netfabb (free) for the translation. Meshlab can also be used a little easier than ParaView.