Karsten Wenzke
-
Content Count
269 -
Joined
-
Last visited
Posts posted by Karsten Wenzke
-
-
Hey,
Please install Openfoam 2.3.1 the scripts you are using are not working with openfoam 3.0. You can find it on the same download site.
They slightly changed the input scripts from 2.3.x to 3.0 and I cannot remember which one exactly.
They merged 2 scripts files into 1.
You are doing the homework exercise for the SDD course right?
I have created the documents for it ;-)
Cheers,
Karsten
-
Hey,
You cannot change the points directly. you need to change/adjust the Parameters in the scope "Parameters".
If you change their values the ship hull will be updated.
In addition you can also try to change the curves in the scope "functions"
Hope this helps.
Cheers,
Karsten
-
Hey Jaap,
Thanks for the report, we will try it as soon as you have uploaded the file.
Create an archive (zip, tar, rar) of the iges and upload it.
Cheers,
Karsten
-
The Brep wants to sue the matching start and end edges of the surfaces. If you shorten the volute surface a bit the Brep will be created with no problems.
You need to create the tongue area anyway.
Depending on you tongue approach just carry on with a trimmed volute surface and create the total volute brep at a later stage.
Cheers,
Karsten
-
-
-
Hey Harry,
It is not possible to have such an export option in CAESES. As you wrote the bspline curves are in the iges and it is also correct to have all the other entities as well because they are need to be able to recreate the brep.
Rhino can read both iges files.
You have two options now in my opionion:
1) Model the ship only with surfaces in caeses then you do not have the problem at all.
Why do use the brep to model the ship? In general the brep is not needed until you need to have a watertight geometry or need to cut a hole in the hull.
or 2) Contact the Napa support and make them aware that their Iges Interpreter has some trouble with the iges file and maybe they can do something about it.
If you like you can share the project with us here in the forum or send it to me via mail then I'll be able to give some advices.
Cheers,
Karsten
-
Dear Harry,
You can create a zip archive and upload them again. There are some upload restrictions to file endings and the maximum size of the attached files.
In the end it is a matter of the Napa Iges interpreter.
Cheers,
Karsten
-
exactly :-) that is stated in the the document you send and you have agreed to :-)
-
Hey Franceco,
simply click the ok button at the end. After 180 days of CAESES FREE you need to accept the General terms of use again.
If this does not solve your problem. It would be great if you could attach a picture of that message.
Cheers,
Karsten
-
Hey Sami,
I would recommend the OpenFOAM for windows from Sim-Flow https://sim-flow.com/download/openfoam-windows/.
It is really easy and you do not really need to change the allrun script of our openfoam tutorial.
I've never used the OpenFOAM for windows which you mentioned.
This is an example allrun script for windows for the simflow OF which you need to adapt the allrun script of the sduct tutorial.
::Meshing surfaceFeatureExtract blockMesh snappyHexMesh -overwrite :: solving simpleFoam ::postprocessing :: equivalent for touch on linux systems echo .> case.foam patchAverage p -latestTime sduct_Inlet > pin.dat patchAverage p -latestTime sduct_Outlet > pout.dat
Cheers,
Karsten
-
Hey Oliver,
1) We do not have a latex listings for FPL. Sorry.
2) We also do not have a list of all commands for the easy to copy and paste.
All commands are documented and can be found in the documentation browser.
P.s. If you create a listing for FPL it be awesome if you share it with the CAESES community by the time it is finished.
Cheers,
Karsten
-
Hey Oliver,
If you want to use your so called ascii art you do need to change the font of CAESES.
1) menu > file > settings
2) click on appearance
3) scroll down to fonts and choose for example curier 10 Pitch and choose Font style regular
It is not possible to change the font style of the console individually therefore this is the only solution.
Now your echo created inside the feature looks similar to the console and vice versa.
The reason is you need to choose a mono spaced font.
You still have one space to much in line 20 in your feature definition or you need to add one space in line 21.
Cheers,
Karsten
-
1
-
-
Hey Emre,
There is a Tutorial included in CAESES in the documentation browser > Tutorials > Integration > ansy.
Which guides you through the process.
What do you mean by "with its parameters"?.
You can export the impeller as iges, step, stl and tetin (ICEM CFD file).
Cheers,
Karsten
-
cp: cannot stat ‘../baseCase/constant/polyMesh’: No such file or directory
This is the line which is causing the errors which are appearing afterwards.
The path "basecase" seems to be wrong. But without having seen the project file it is really hard to help further.
Can you upload the project file. It would help to identify the problem.
Cheers,
Karsten
-
Hey Emre,
If you are a student and you are using the CAESES academic version you can use the batch mode.
Simply follow these instructionshttps://www.caeses.com/forum/index.php?/topic/67-how-to-get-a-student-license/ and we will update your license in order be able to use the student version.
Cheers,
Karsten
-
take a look at this post and note that the batch mode is not part of the free version.
Cheers,
Karsten
-
Dear Hamid,
For the internal optimization you should take a look at the tutorial "Fulfilling geometrical Constraints".
This is the same Carlo described.
I think, the best way is defining the “persistent “ feature to have the capability of run in each design process, also, the outputs should define outside of the feature as you said. Thus, applying the” preprocessing commands” result in change the outputs according to input for each design.
This is exactly what the pre porcessing command does.
In addition you cannot use a persistent feature because the feature would change its one arguments which is not allowed because it is an infinite recursion.
Let me know if you need any further assistance and/or explanations.
A project file and a more detailed description would be helpful in order to be able to solve and understand your workflow,
Cheers,
Karsten
-
Awesome. Have fun.
-
Hey Aldi ,
On linux systems there is no need to install CAESES.
You only need to extract the archive.
Which is also stated below the download link on our website.
"For Linux, extract CAESES.tar.gz, change the working directory to the CAESES® folder and start with: ./CAESES"
Hope this solves your problem.
Cheers,
Karsten
-
Hey Aldi ,
On linux systems there is no need to install CAESES.
You only need to extract the archive.
Which is also stated below the download link on our website.
"For Linux, extract CAESES.tar.gz, change the working directory to the CAESES® folder and start with: ./CAESES"
Hope this solves your problem.
Cheers,
Karsten
-
Hey Kenneth,
First of all, thank you for the report.
Which operating system do you use?
If it is some sort of Linux distribution.
I’d like you to try the following process (second post by Konrad) and let us know whether it solved your problem or not.
Cheers,
Karsten
-
-
Hey,
However, there are some small drawbacks, seems like you cannot assigne the same name to a geometry object and a color.
You are right. The reason is that geometry objects and colors are both objects.
Cheers,
Karsten
CAESES connection with openFOAM in Windows
in Software Connections
Posted · Report reply
Hey,
Did you install simflow with Administration rights?
Right click on the executable of simflow (Installation) and choose "run as Administrator"
Seems that the links in the System have not been set properly.
Can you try to reinstall simflow.
Let me know if it helps.
@Carsten: Sure the Software connector is in that file already? If I remember correctly is that the stage right aber die variable geometry and no Connection has been set up. the ..03 or 04 is the one after the Software connector has been Setup. But then the half of the assessment is done already.
Have a nice weekend
Cheers,
Karsten