That's why the "". I've started using paraview as I can look specifically at what I want, even compare 2 cases side-by-side. Not a complaint at the auto output.
- Login or Register
No account yet? Sign up
That's why the "". I've started using paraview as I can look specifically at what I want, even compare 2 cases side-by-side. Not a complaint at the auto output.
That will soon be possible in MFlow. Once more there are odd Windows issues to fix first. I am really hope this Ubuntu on Windows will actually work and solve all of the Windows related issues. Newer OF versions even have an adjoint surface solver, which would be ultra cool for MVRC.
Right now this is not an option in MFlow and do not think I want it to be an option. You can manually delete stuff in the sampleDict file, located in the system folder.jjn9128 wrote: ↑Tue Apr 07, 2020 8:39 pmHow do we change what images are output? e.g. I'm getting an "out of space" error because I'm outputting 50 X slices, but all I'm really interested in is CpTot - can I deactivate Ux, Cp...etc? Similarly I'm not interested in the +/- 0.5 on the surface Cp contour.
In the settings, you can switch the color map, used for post-processing, even after the run is done, just apply the new settings, build the case once more, do not solve again and hit the post-process button.wb92 wrote: ↑Tue Apr 07, 2020 5:27 pmSo MFlow_2003 works like a charm
Easy, it's not drama with colors. It's just that in previous Cp slices there was more contrast between colors, so you could see the areas where for example FW, RW, diffuser works the strongest. It was just bit easier to quickly spot it on, but as mentioned, no drama. Glad that software works without errors and initial phase of WBR20 development can go without delays ^^
I use very fancy software called "pictures" to compare cases
it's enough when you can output around 100 pics for each axis. I noticed that, but was afraid to use
still I'm fine with what is available, on top of that I have bit more tools to compare cases than last year, so let's see how it will go now.
Yes but can you do this with ya fancy "pictures"?
Not automatically, but I don't need oilflow so often.jjn9128 wrote: ↑Thu Apr 09, 2020 5:46 pmYes but can you do this with ya fancy "pictures"?
https://qd1lqw.db.files.1drv.com/y4mfr0 ... pmode=none
interesting that I guess most of us have bit different approach to post-pro data
Templates are the 2019 V09.CAEdevice wrote: ↑Thu Apr 09, 2020 6:31 pmSorry guys, this year I have been bit too busy and I did not follow this thread and MVRC. May I ask you a summary?
Is the CAD template (as the rulebook) exactly the same of 2019? Are there any changes about the mesh and boundary condition in the software (I mean, the numerical results of 2019 are comparable to this year simulations)?
Yeah 2 cases. I'm trying to get Y250 and subsequent vortices working in harmony so I'm wanting to seen the rotation. ATM they're getting sucked under the floor rather than passing the around the bargeboards.wb92 wrote: ↑Thu Apr 09, 2020 6:00 pmNot automatically, but I don't need oilflow so often.
Hmm... what's interesting on your picture is that oilflow lines are not symmetrical. There are 2 cases side-by-side, right?
I can do that with setting 2 pictures windows side-by-side also, in the end I don't need to have them like that, but what works for you it works
I've been putting them in "default" which has been working.TalnoRacing wrote: ↑Sat Apr 11, 2020 9:09 amI'd like to ask for help.
In which folders in the MFlow case file should I place the driver helmet, halo, gearbox, exhaust, suspension and mirrors? The wheels have dedicated folders but I am unsure about the other parts. Also, what should I name these? If I use the default template names I get an error message in MFlow.
