mc96107 / blenderfds Goto Github PK

It would be nice to be able to specify a fire via material, but not have that 
material directly applied to all surfaces of an obstruction.  At the moment, 
the material definition appears to only be exported if it is attached to an 
object.  

This means that I either have to create a separate vent that is positioned on 
the obstruction and has the material applied to it, or I apply the material to 
an OBST, use the SURF_ID6 parameter and then manually edit the output FDS file 
to delete the residual SURF_ID entry.

It would be nice to have the ability to apply a material to only one face, or 
an entire object without manually editing the FDS File.

>  Dear Mr Gissi, 

> im quite new in the field of Fire Simulations but i think already quite 
> familiar with Blender and its interface for FDS. Im working on risk 
> analysis for Tunnels, lately trying to build my tunnel models in Blender 
> for more precise analysis. Now im stuck at the real end of my first 
> complete model. I was trying to integrate the DEVC components for 
> visibility in the middle of the tunnel's cross-section. The tunnel is about 
> 100 m long, so i didnt want to waste time on copying every single device 
> over and over again to finally get the wished number of sensors. And I 
> thought: 'Hey! Let's use this cool array tool!' In Blender it worked fine, 
> i adjusted everything to my needs, but after exporting it to FDS i saw that 
> only the originial devc had been exported, the copies of the array tool had 
> been ignored. How can i fix this? If this isn't possible i would have to 
> capitulate using Blender for my modeling of the tunnels. It'd be just 
> impracticle. I've already been searching - i think - all of the group 
> discussions and support forums, but nobody seemed to face this problem. I 
> hope u can help me :) 


> Thank you for your attention and the best greetings from Switzerland, 


> Julius Ernst 

Hi Julius, 
this seems as a BlenderFDS bug to me. 


Please open an issue and attach an example case. 
As a workaround I suggest you to save a backup copy of your project and 
then "apply" the modifier. 
Please, tell me if this workaround works for you. 


I CC to the blenderfds group, so that it becomes shared knowledge. 
Best regards, 
Emanuele Gissi 


Hi Mr Gissi,



thank for your fast response! I'll post it today on the blenderfds page if i 
get enough time for it :) About clicking "apply": already done it :S But when i 
got desperate and thought i just wasn't smart enough i tried it out just with a 
simple mesh and some arrayed boxes and it worked. Just the DEVC lines aren't.



Thank you again,


Julius Ernst

Hi,
I would really appreciate your help on this one.  Its just started happening, 
and only for this specific obstruction.  
See attached file
1. Open the file
2. Select the OBST_Slab object
3. Set XB to Voxel

On my computer it crashes immediately.  No output to the console.

OBST is manifold... I checked that first.

Running BlenderFDS 1.2.3 on Blender 2.63 windows 7 Pro (64bit).

Any assistance would be appreciated, as I am trying to run a simulation for a 
client that needs to get started ASAP.

Regards,

Craig

Background scaling and positioning does not work correctly when the view is not 
set to 'top'.

It is possible to apply the SURF namelist to an object, causing an error on 
export.  SURF is only implemented for materials, so applying it to an object 
causes an error due to the lack of a diffuse_color attribute for objects.

Solution:  Implement a warning message to direct users to the materials tab.

Hello!

I installed IronPython 2.6 (Windows XP sp3),

then tried to compile __ init__.py bf_config.py bf_export.py bf_geometry.py 
bf_ui.py

unfortunately did not work ...

do not tell me how to compile your project in IronPython?

with respect, Serge

What steps will reproduce the problem?
1. export the fds file and you'll see the problem
2.
3.


What is the expected output? What do you see instead?
(Tthe attached .fds file has a modeling bug which I am working out involving 
vents - ignore this error when you run the model - i have not figured this one 
out yet, or else I would have removed it before sending this file in. Sorry!)

The expected output are EXTERNAL BC faces that are similar to those in the 
example file test_1.fds as below:

! External bc

&VENT ID='External bc', FYI='Boundary cond at domain borders', SURF_ID='OPEN', 
PBZ=3.000, /

&VENT ID='External bc', FYI='Boundary cond at domain borders', SURF_ID='OPEN', 
PBY=-2.500, /

&VENT ID='External bc', FYI='Boundary cond at domain borders', SURF_ID='OPEN', 
PBX=-2.500, /

&VENT ID='External bc', FYI='Boundary cond at domain borders', SURF_ID='OPEN', 
PBY=2.500, /

&VENT ID='External bc', FYI='Boundary cond at domain borders', SURF_ID='OPEN', 
PBX=2.500, /



I am getting output such as the below:

&VENT ID='EXTERNAL BC', FYI='BOUNDARY COND AT DOMAIN BORDERS', SURF_ID='OPEN', 
PBZ=3.034, /
&VENT ID='EXTERNAL BC', FYI='BOUNDARY COND AT DOMAIN BORDERS', SURF_ID='OPEN', 
PBZ=3.034, /
&VENT ID='EXTERNAL BC', FYI='BOUNDARY COND AT DOMAIN BORDERS', SURF_ID='OPEN', 
PBZ=6.740, /
&VENT ID='EXTERNAL BC', FYI='BOUNDARY COND AT DOMAIN BORDERS', SURF_ID='OPEN', 
PBZ=-0.672, /
&VENT ID='EXTERNAL BC', FYI='BOUNDARY COND AT DOMAIN BORDERS', SURF_ID='OPEN', 
PBZ=3.034, /
&VENT ID='EXTERNAL BC', FYI='BOUNDARY COND AT DOMAIN BORDERS', SURF_ID='OPEN', 
PBZ=3.034, /

You can see I get unusual numbers (not the numbers for my planes that are in 
the DOMAIN object). The DOMAIN object should be the same as the EXTERNAL BC 
object (one was created from the other).

What version of the product are you using? On what operating system?
Latest version:
FDS-Smokeview bundle created 
Fri 10/29/2010 
11:28 PM

Versions:

-------------------------- 

Fire Dynamics Simulator

Version: 5.5.3; MPI Disabled; OpenMP Disabled
SVN Revision Number: 7031
Compile Date: Fri, 29 Oct 2010

Consult FDS Users Guide Chapter, Running FDS, for further instructions.

Hit Enter to Escape...

-------------------------- 
Process   0 of   0 is running on bfrl-l-851084.nist.gov

Fire Dynamics Simulator

Version: 5.5.2; MPI Enabled; OpenMP Disabled
SVN Revision Number: 7019
Compile Date: Tue, 26 Oct 2010

Consult FDS Users Guide Chapter, Running FDS, for further instructions.

Hit Enter to Escape...

-------------------------- 
 fds2ascii 2.1.0 Revision: 6404

-------------------------- 

Smokeview 5.6 - Oct 29 2010

Version: 5.6
Smokeview (64 bit) Revision Number: 7032
Compile Date: Oct 29 2010
Platform: WIN64  (Intel C/C++)

-------------------------- 

Smokediff

Version: 1.0.3
SVN Revision Number: 7013
Compile Date: Oct 29 2010
Platform: WIN64

-------------------------- 

Smokezip

Version: 1.4
SVN Revision Number: 6965
Compile Date: Oct 20 2010
Platform: WIN32

-------------------------- 

background

Version: 1.0
SVN Revision Number: 6532
Compile Date: Oct 29 2010


Please provide any additional information below.

Having installed Blender 2.58 successfully and then downloaded blenderfds 
1.0.1.zip I have blenderfds in the addon list but will not allow activation, 
does not appear to have Blenderfds folder in addons?

What steps will reproduce the problem?
1.  open blender file
2.  try to export to fds/smv file
3.

What is the expected output? What do you see instead?

Error message:

BlenderFDS: Start exporting to FDS case file, current scene: Scene
Traceback (most recent call last):
  File "C:\Users\solenick.CSE\AppData\Roaming\Blender Foundation\Blender\2.63\sc
ripts\addons\blenderfds\__init__.py", line 69, in execute
    return bf_export.save(self, context, **self.as_keywords(ignore=("check_exist
ing", "filter_glob")))
  File "C:\Users\solenick.CSE\AppData\Roaming\Blender Foundation\Blender\2.63\sc
ripts\addons\blenderfds\bf_export.py", line 257, in save
    bpy.ops.material.bf_create_predefined()
NameError: global name 'bpy' is not defined

What version of the product are you using? On what operating system?

BlenderFDS 1.9.9RC1
Blender 2.64 beta
Windows7 x64

Please provide any additional information below.

Follows from discussion board:

https://groups.google.com/forum/?fromgroups#!topic/blenderfds/1XIhL8msR-E

I have attached the cleaned Blender file you kindly provided to me.  All 
surfaces are manifold and error still occurs.  Hence, occurred with or without 
manifold surfaces.

What steps will reproduce the problem?
1.load empty blender file and create a simple cube
2.select voxel -> show voxels
3.

What is the expected output? What do you see instead?
- no change in position of voxel

What version of the product are you using? On what operating system?
3

Please provide any additional information below.

There is no problem.
I have attached the  __init__.py file where I modified the default value for 
the blender objects to all be exported to the FDS case from "false" to "true"

this saves hours in not having to click the square on "fds obst" button. 


ALSO
A sugestion is to create a button that will select all objects and set 
SAWTOOTH=.Frue

The code from Emanuele is below:

import bpy
# Get objects
obs = {ob for ob in bpy.data.objects if ob.bf_export and ob.bf_nl=="OBST"}
# Set SAWTOOTH=.FALSE. to True
for ob in obs:
    ob.bf_sawtooth = True

Export this kind of objects:
http://code.google.com/p/fds-smv/issues/detail?id=1492

Use numpy to speed up the exporting script.

Blender UI freezes for some seconds while exporting large files.
I have not found a way to show feedback to the user (progress bar?).
Probably Blender 2.5 alpha2 is not mature enough.

What steps will reproduce the problem?
Exporting from Blender to FDS.

What is the expected output? 
If it's possible, the FDS lines sorted alphabetically according to its FDS 
command (&...) and/or its ID.

What version of the product are you using? On what operating system?
Blender 2.61 and BlenderFDS 1.0.3

Thanks

Add MPI_PROCESS to MESH namelist.

    Usually in a multi-mesh calculation, each mesh is assigned its own
    process, and each process its own
    processor. However, it is possible to assign more than one mesh to a
    single process, and it is possible to
    assign more than one process to a single processor. Consider a case
    that involves six meshes:
    &MESH ID='mesh1', IJK=..., XB=..., MPI_PROCESS=0 /
    &MESH ID='mesh2', IJK=..., XB=..., MPI_PROCESS=1 /
    &MESH ID='mesh3', IJK=..., XB=..., MPI_PROCESS=1 /
    &MESH ID='mesh4', IJK=..., XB=..., MPI_PROCESS=2 /
    &MESH ID='mesh5', IJK=..., XB=..., MPI_PROCESS=3 /
    &MESH ID='mesh6', IJK=..., XB=..., MPI_PROCESS=3 /
    The parameter MPI_PROCESS instructs FDS to assign that particular mesh
    to the given process. In this case,
    only four processes are to be started, numbered 0 through 3. Note that
    the processes need to be invoked in
    ascending order, starting with 0. Why would you do this? Suppose you
    only have four processors available
    for this job. By starting only four processes instead of six, you can
    save time because ‘mesh2’ and ‘mesh3’
    can communicate directly with each other without having to transmit
    data using MPI calls over the network.
    Same goes for ‘mesh5’ and ‘mesh6’. In essence, it is as if these mesh
    pairs are neighbors and need not send
    mail to each other via the postal system. The letters can just be
    walked next door.

Tried loading test_suite.blend into Blender 2.5 Alpha, but it's rejected with 
the message "test_suite.blend" is not a Blender file.

I created a multi-mesh model with different grid sizes.  The poisson optimiser 
messed up the grid alignment for me.  I had one mesh with 0.4 grids, the other 
was with 0.2.  when I exported it, the IJK values had changed on one mesh and 
it no longer aligned.

Blender 2.61 on Windows 7.

What version of the product are you using? On what operating system?

1.0.2 stable with Blender 2.58

Please provide any additional information below.

A nice enhancement idea would be to put in an option to write out the smokeview 
ge1 CAD file from the blender geometry.  This would provide better viewing 
options in smokeview after a simulation, and would allow comparison in 
smokeview between the CAD and the BlenderFDS output.  Just a suggestion.

[deleted issue]

What steps will reproduce the problem?
1. Faces cannot be exported as voxels
2.
3.

What is the expected output? What do you see instead?
Create "voxelized" faces for non-rectangular vents. Must somehow conserve area 
or at least report the produced area in a comment in the FDS script.

What version of the product are you using? On what operating system?
blender-2.5-alpha2-win32 & BlenderFDS_0.44

Please provide any additional information below.

Hi,

I'm new in FDS's world and I'm trying to import a .STL file with blender and 
then export it as a .fds file thanks to blenderfds.


What steps will reproduce the problem?
1.I import my file
2.I click on the Object panel, then check 'FDS OBST', select 'Voxel' and 
THICKEN=.TRUE
3.I click on the Material panel, add a default material on FDS SURF
4.I try to export the file.fds
5.This error message appears AttributeError 'RemeshModifier' object has no 
attibute 'remove_disconnected_pieces' and a myfile_tmp object has been created 
with an object modifiers option.

What should I do ?

What version of the product are you using? On what operating system?

I'm using blender 2.67 and blenderfds 2.0.1

Regards

More of a suggested change than a bug.  The current location of the button 
causes the IJK sliders to jump to the left as they are resized to accomodate 
the correction button.  Can this be moved to below the sliders?  at the moment 
I try to click rapidly, and the slider disappears from under my mouse.

Use of IJK does appear to help with sorting out multiple meshes.  I like it!

Feature Request.

To aid in initial positioning of objects, I think it may be useful to have a 
button in the MESH Object control panel that creates a grid on the min X,Y and 
Z faces of the Mesh object.  The divisions can be created usig the loop cutting 
feature, which can be set to make cuts based on the IJK values set for the mesh.

Possible procedure would be:
1.  create a cube.  theis would be a temporary object, similar to the view 
voxel object.
2.  parent it to the MESH
3.  Delete to Max X,Y and Z faces.
4.  Iterate through I,J and K using the loop cut, with the number of cuts set 
to I-1, J-1 and K-1.
5.  Set the new object to bounding box or wire view so it doesn't visually 
clutter the scene.

The resulting object can be used to snap to vertices when moving things around 
within the mesh.  can also be used to snap object faces when re-sizing, 
avoiding the need to punch in the coordinates (which I find tedious).

Thoughts?

Object properties panel title is not always refreshed when selecting
objects in the outliner.
Newer Blender versions fix this issue.

DEVC_ID parameter management is easy to implement.
Consider the addition.