1
PyroSim / Re: Resume parallel simulation
« on: March 01, 2010, 01:48:25 pm »
FDS 32bit Version 5.4.3
Thunderhead Engineering Forum
- April 16, 2021, 10:30:09 pm
- Welcome, Guest
News:
Forum moved to https://forum.thunderheadeng.com
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1] 2
2
PyroSim / Re: Resume parallel simulation
« on: February 25, 2010, 09:32:16 am »
Attached the FDS file, but it is a complicated one. I did not have the time to simplify the file and find out where the problem is. Moreover I attach the "FDS simulation" window. As you see there is no error, but after more that 10 minutes there is no further time steps. The only action I can do is manually kill the program via Taskmanager.
3
PyroSim / Resume parallel simulation
« on: February 24, 2010, 07:20:21 am »
Resuming stopped simulations has problems at large meshes.
I''m actually working on a simulation with 300''000 cells, equally split in 2 meshes. The simulation runs in parallel mode (I have a dualcore CPU).
After stopping the simulation, the "resume parallel simulation" doesn''t work properly.
When doing the "resume parallel simulation", the "FDS simulation" windows opens properly and everything seems right. The "Time Elapsed" clock continues to increase , but the simulation does not restart, i.e. no further time steps are shown. I waited for 50 about minutes (confirmed by the Elapsed Time clock) and then had to close pyrosim manually.
This doesn''t happen when doing the non parallel "resume simulation", which restarts after a couple of seconds (even if applied to a previously parallel running simulation)
I tested both the 32 and 64 bit pyrosim versions, the former on a dualcore and the latter on a quadcore processor, with same results.
Somebody knows where is the problem on parallel simulations? Thanks
Michele
I''m actually working on a simulation with 300''000 cells, equally split in 2 meshes. The simulation runs in parallel mode (I have a dualcore CPU).
After stopping the simulation, the "resume parallel simulation" doesn''t work properly.
When doing the "resume parallel simulation", the "FDS simulation" windows opens properly and everything seems right. The "Time Elapsed" clock continues to increase , but the simulation does not restart, i.e. no further time steps are shown. I waited for 50 about minutes (confirmed by the Elapsed Time clock) and then had to close pyrosim manually.
This doesn''t happen when doing the non parallel "resume simulation", which restarts after a couple of seconds (even if applied to a previously parallel running simulation)
I tested both the 32 and 64 bit pyrosim versions, the former on a dualcore and the latter on a quadcore processor, with same results.
Somebody knows where is the problem on parallel simulations? Thanks
Michele
4
PyroSim / EVAC: Avatar color
« on: February 21, 2010, 02:20:30 pm »
In the EVAC Menu "evac -> properties -> output" one can define avatar color (both alive and death). By defining "Color By: PERS", the chosen colors should be seen in smokeview when activating the "SHOW/HIDE->Humans->HUMAN_COLOR".
The "death" color setup is working fine in smokeview, but not the alive avatar color, which remain in standard blue.
How can I see the desired avatar alive color?
Thanks
Michele
The "death" color setup is working fine in smokeview, but not the alive avatar color, which remain in standard blue.
How can I see the desired avatar alive color?
Thanks
Michele
5
PyroSim / Re: EVAC : disable mesh
« on: February 18, 2010, 02:05:32 pm »
Well, I'm doing it to perform some tests, and it works.
It's just about removing the ampersand "&" (in the generated FDS file) in front of the FIRE mesh line if one wants to look at the evacuation, viceversa remove it from the EVAC mesh line to look at the fire simulation.
The only "unpleasand" thing is that I have to export the FDS file from Pyrosim, modify it, and run the simulation manually from the cmd-line. Nevertheless i guess it is faster than disabling all the command from pyrosim.
It's just about removing the ampersand "&" (in the generated FDS file) in front of the FIRE mesh line if one wants to look at the evacuation, viceversa remove it from the EVAC mesh line to look at the fire simulation.
The only "unpleasand" thing is that I have to export the FDS file from Pyrosim, modify it, and run the simulation manually from the cmd-line. Nevertheless i guess it is faster than disabling all the command from pyrosim.
6
PyroSim / Re: EVAC : disable mesh
« on: February 18, 2010, 04:17:54 am »
Charlie,
after a couple of week I'm coming back to the topic of disabling meshes.
The disabled mesh will still be considered in case of the presence of events (VENTs, OBSTs, ...) that recall it
Therefore once the complete fire+evacuation simulation is set up, the only way to test the fire and evacuation separately is to manually delete the ampersand "&" from the fds file and run it manually from the cmd-line, right?
Michele
after a couple of week I'm coming back to the topic of disabling meshes.
The disabled mesh will still be considered in case of the presence of events (VENTs, OBSTs, ...) that recall it
Therefore once the complete fire+evacuation simulation is set up, the only way to test the fire and evacuation separately is to manually delete the ampersand "&" from the fds file and run it manually from the cmd-line, right?
Michele
7
PyroSim / Re: Slab - crash
« on: February 15, 2010, 10:02:35 am »
Just create a slab that crosses the meshes boundaries and try to visualize the "record View" and you should have the crash notification.
I'm attaching the log file. Pay attention that I had to change the file extention to "txt" in order to attach it.
Michele
I'm attaching the log file. Pay attention that I had to change the file extention to "txt" in order to attach it.
Michele
8
PyroSim / Slab - crash
« on: February 12, 2010, 01:45:49 am »
Hi,
when dealing with "SLAB" feature, Pyrosim crashes when the slab is outside the mesh boundaries.
The crash occur when trying to visualize the Record View, or when trying to run the simulaiton or even only by generating the FDS file.
By multiple meshes, same problem appears when the slab crosses 2 meshes, even though it remains inside the "global" mesh dimensions.
The only solution is to cut the slab in multiple pieces corresponding to mesh boundaries.
Attached the error report.
Thanks for the help
Michele
when dealing with "SLAB" feature, Pyrosim crashes when the slab is outside the mesh boundaries.
The crash occur when trying to visualize the Record View, or when trying to run the simulaiton or even only by generating the FDS file.
By multiple meshes, same problem appears when the slab crosses 2 meshes, even though it remains inside the "global" mesh dimensions.
The only solution is to cut the slab in multiple pieces corresponding to mesh boundaries.
Attached the error report.
Thanks for the help
Michele
9
PyroSim / Re: EVAC : disable mesh
« on: February 05, 2010, 11:01:30 am »
Well, I also did some tests and seemed that the mesh is disabled when there are no line codes that recall the mesh. Attached is my FDS file.
Moreove I'm trying to test a simulation with both a fire and evacuation but I only get a "severe" error message. I'm trying everything to solve the problem.
From FDS discussion it seems to be a bug. I also tried to modify the fds file (not through Pyrosim) but did not get the point...
Thanks for the help on those topics.
Michele
Moreove I'm trying to test a simulation with both a fire and evacuation but I only get a "severe" error message. I'm trying everything to solve the problem.
From FDS discussion it seems to be a bug. I also tried to modify the fds file (not through Pyrosim) but did not get the point...
Thanks for the help on those topics.
Michele
10
PyroSim / EVAC : disable mesh
« on: February 04, 2010, 02:47:20 pm »
Hi,
I'm dealing with Evacuation simulation.
In order to test the set-up before proceeding with the complete simulation it is very useful to enable and disable the fire meshes and evacuation meshes.
In "common" fds code this can easily be done by deleting the ampersand ("&") from the unwanted mesh line.
In Pyrosim that's usually correspond to "disable" the selected object. It usually works but that function has no effect on the meshes (it can be seen from the source code).
Do I have to change some settings or that option doesn't work on Pyrosim?
Thanks for the help
Michele
I'm dealing with Evacuation simulation.
In order to test the set-up before proceeding with the complete simulation it is very useful to enable and disable the fire meshes and evacuation meshes.
In "common" fds code this can easily be done by deleting the ampersand ("&") from the unwanted mesh line.
In Pyrosim that's usually correspond to "disable" the selected object. It usually works but that function has no effect on the meshes (it can be seen from the source code).
Do I have to change some settings or that option doesn't work on Pyrosim?
Thanks for the help
Michele
11
PyroSim / Re: EVAC : Random Seed
« on: February 03, 2010, 10:26:28 am »
Yes, I guess the reason for that command is for debugging and eventually for simulation set-up.
Even in the user's guide it's written "[...] one is saving some CPU seconds [...]".
Even in the user's guide it's written "[...] one is saving some CPU seconds [...]".
12
PyroSim / Re: EVAC : Random Seed
« on: February 03, 2010, 07:40:30 am »
Same with "Calculate Evac Flow Field".
When flagged it return the FDS command "EVACUATION_MC_MODE=.TRUE." which means that the evacuation flow field is NOT (re)calculated. Existing CHID_evac.eff file is to be read (or eventually EFF recalculated if file is not existing).
Am I right?
When flagged it return the FDS command "EVACUATION_MC_MODE=.TRUE." which means that the evacuation flow field is NOT (re)calculated. Existing CHID_evac.eff file is to be read (or eventually EFF recalculated if file is not existing).
Am I right?
13
PyroSim / Material definition
« on: February 03, 2010, 04:03:18 am »
In the description of material pyrolysis, the reaction rate formula is described with pressure (p).
It should be density (rho) as indicated in Chapter 3.4.3 of Tech. Reference Guide, right?
It should be density (rho) as indicated in Chapter 3.4.3 of Tech. Reference Guide, right?
14
PyroSim / Re: Importing FDS+EVAC files
« on: February 03, 2010, 03:16:23 am »
I found new useful stuff on that matter.
There are 2 Users guide manuals on EVAC available on VTT web page.
One is downoladed with name "W119.pdf" from the VTT homepage, the second one can be found at this link
http://www.vtt.fi/proj/fdsevac/fdsevac_documents.jsp
The first link on this page opens a newer manual, which can be recognized by the lack of formatted index table and cross references.
This manual is related to FDS 5.4.1, Evac 2.2.0 versions (as can be seen on chapter 11 Conclusion, and not from the first page).
Therefore Pyrosim should have FDS version 5.4.1 and EVAC 2.2.0
There are 2 Users guide manuals on EVAC available on VTT web page.
One is downoladed with name "W119.pdf" from the VTT homepage, the second one can be found at this link
http://www.vtt.fi/proj/fdsevac/fdsevac_documents.jsp
The first link on this page opens a newer manual, which can be recognized by the lack of formatted index table and cross references.
This manual is related to FDS 5.4.1, Evac 2.2.0 versions (as can be seen on chapter 11 Conclusion, and not from the first page).
Therefore Pyrosim should have FDS version 5.4.1 and EVAC 2.2.0
15
PyroSim / Re: Importing FDS+EVAC files
« on: February 03, 2010, 01:48:08 am »
Yes, I agree that there is a lot of movement in FDS and EVAC development and it is a big deal to stay up to date with all new revisions.
Nevertheless, when reading the various user's guide, it is clear that it is very important to understand which version of FDS and EVAC one is dealing with
I have installed Pyrosim which works with FDS 5.4.1 version. When running an simulation I can see that it uses EVAC version is 2.2.0 (open CHID_evac.out to check the installed EVAC version).
This means that even though Pyrosim is not boundled to latest FDS version (which should be 5.4.3) , it works with the lastest EVAC version.
Note: beside Pyrosim I also have latest FDS version separately installed on my computer, perhaps there is an kind of overlapping of used versions?
Nevertheless, when reading the various user's guide, it is clear that it is very important to understand which version of FDS and EVAC one is dealing with
I have installed Pyrosim which works with FDS 5.4.1 version. When running an simulation I can see that it uses EVAC version is 2.2.0 (open CHID_evac.out to check the installed EVAC version).
This means that even though Pyrosim is not boundled to latest FDS version (which should be 5.4.3) , it works with the lastest EVAC version.
Note: beside Pyrosim I also have latest FDS version separately installed on my computer, perhaps there is an kind of overlapping of used versions?
Pages: [1] 2