Search found 112 matches
- Wed Apr 01, 2020 11:12 am
- Forum: trouble-shooting
- Topic: error (72) floating overflow
- Replies: 10
- Views: 2541
Re: error (72) floating overflow
Hi Josh, Mike, the floating point exception occurs in both version - Windows and Linux - while the TQ library copes with the requested calculations and thermo-dynamic data. Not all exceptions are caught in this library. Usually, this does not make the results worse because results from such errornou...
- Mon Mar 30, 2020 9:59 am
- Forum: trouble-shooting
- Topic: error (72) floating overflow
- Replies: 10
- Views: 2541
Re: error (72) floating overflow
I do not know from any problem regarding changing OS between creation and usage of GES5 files. To exclude this generally possible source of error, testing would be best. MICRESS 6.4 uses a TQ library from Thermo-Calc 2017a. As far as I know, Thermo-Calc does not break backwards compatibility since 2...
- Mon Mar 23, 2020 3:40 pm
- Forum: trouble-shooting
- Topic: Issues running simulations in parallel version
- Replies: 8
- Views: 1695
Re: Issues running simulations in parallel version
Please have also a look at your sequential TabP.
When I activated nucleation in 6.2, most of the time was spent in TQ. This is a serial part and running it in parallel will give you no benefit.
Parallel is good for diffusion, stress, etc.
Ralph
When I activated nucleation in 6.2, most of the time was spent in TQ. This is a serial part and running it in parallel will give you no benefit.
Parallel is good for diffusion, stress, etc.
Ralph
- Mon Mar 23, 2020 3:35 pm
- Forum: trouble-shooting
- Topic: Issues running simulations in parallel version
- Replies: 8
- Views: 1695
Re: Issues running simulations in parallel version
The license can be updated independent of the installation.
I guess only the license was updated.
Ralph
I guess only the license was updated.
Ralph
- Mon Mar 23, 2020 3:27 pm
- Forum: trouble-shooting
- Topic: Issues running simulations in parallel version
- Replies: 8
- Views: 1695
Re: Issues running simulations in parallel version
Don't know.
I will send you the download details for 6.4.
Ralph
I will send you the download details for 6.4.
Ralph
- Mon Mar 23, 2020 1:38 pm
- Forum: trouble-shooting
- Topic: Issues running simulations in parallel version
- Replies: 8
- Views: 1695
Re: Issues running simulations in parallel version
Josh, reading molar volumes from database is possible with MICRESS 6.4 and above. You are using 6.2 in parallel. For the first 400 s, I see no differences between serial and parallel version. So far, so good, at least in comparing versions. Nucleation: Bernd gave me the hint that setting the number ...
- Fri Mar 20, 2020 5:23 pm
- Forum: trouble-shooting
- Topic: Issues running simulations in parallel version
- Replies: 8
- Views: 1695
Re: Issues running simulations in parallel version
Never seen something like this.
Which MICRESS version do you use?
Can you share the input files? At least with support@micress.de
Best,
Ralph
Which MICRESS version do you use?
Can you share the input files? At least with support@micress.de
Best,
Ralph
- Wed Mar 11, 2020 10:49 am
- Forum: new functionalities
- Topic: Python API
- Replies: 3
- Views: 1438
Re: Python API
Thanks! I will forward this to Lukas.
Ralph
Ralph
- Tue Mar 10, 2020 7:35 pm
- Forum: new functionalities
- Topic: Python API
- Replies: 3
- Views: 1438
Re: Python API
No, there is no general Python API for generating input available. Would be very complex to implement that, I think. Of course, we made already parameter studies by Python scripts. I prefer to use place holders in a driving file template and write a script which instances this template with a specif...
- Mon Mar 09, 2020 11:06 am
- Forum: pre-processing
- Topic: output of each step
- Replies: 4
- Views: 1228
Re: output of each step
The restart file is like a snapshot of the current state of the simulation. There is no history included. It's not possible to do a restart from an intermediate time step with that file. Of course, it is possible to copy the restart file after each output with an external script (or manually). Given...