FDS 6.7.1, SMV 6.7.4 maintenance release

[randy.m...@gmail.com]

Dear Users,

Maintenance releases for FDS and Smokeview have been posted at the NIST FDS-SMV Website.

In the event of a government shutdown, bundles can always be obtained directly from GitHub releases (but going through the NIST webpage makes our managers happy).

Release notes and installation instructions can be found here.

Kevin will follow up with a few more comments about the updates in this version.

Please let us know if you have any problems.

Best,

The FDS Development Team

[Andrew]

Hi

When installing or unzipping the Linux vesion of the install, the bin/lib64 folder appears to be empty.  I was able to fix by copying the missing files from an older version of the install.

Thanks

Andrew

[Glenn Forney]

thanks for the heads up 

--
You received this message because you are subscribed to the Google Groups "FDS and Smokeview Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fds-smv+u...@googlegroups.com.
To post to this group, send email to fds...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fds-smv/02383603-311f-4c46-9756-147b79b50404%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Glenn Forney

[Glenn Forney]

were you having trouble running fds before copying these files?  the files along with several others are now located in bin/INTEL .  I made the change because this INTEL directory is a subset of what is provided by Intel when the Intel mpi libraries are installed.  I wanted to make the directory structure the same as much as possible.  The bundle should not have created a LIB64 directory or path entries for it.  I'll make this correction for the next bundle.

Note you need to update your startup files to point to the INTEL directory (the FDS6VARS.sh script that comes with the bundle does this)

On Mon, Feb 11, 2019 at 9:21 AM 'Andrew' via FDS and Smokeview Discussions <fds...@googlegroups.com> wrote:

--

You received this message because you are subscribed to the Google Groups "FDS and Smokeview Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fds-smv+u...@googlegroups.com.
To post to this group, send email to fds...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fds-smv/02383603-311f-4c46-9756-147b79b50404%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Glenn Forney

[Andrew]

Ah that explains it.  The way we are using FDS is as a module on a HPC cluster.  I hadnt appreciated that the file structure had changed for this release as just copied the previous modulefile and updated the version number.

In that case if you undertake the install and the FDS6VAS.sh script runs it should all be fine.  If its being created as a module it just needs the new variables added to a modulefile.

Thanks

Andrew

[Glenn Forney]

good.  look in FDS/FDS6/bin/modules for a module named FDS6 .  You'll see an entry for LIB64 that I will take out but should work for the location you installed fds

To view this discussion on the web visit https://groups.google.com/d/msgid/fds-smv/183300fb-6630-4378-b343-cce427e96a43%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Glenn Forney

[C Irvine]

Hi, I attempted to download this version but during the install I got the following error: "Too many arguments in command line. 8 was unexpected at this time." This was after saying yes to a standard installation. Any ideas as to what I'm doing wrong?

Cheers,

Calum

[Randy McDermott]

Something looks wrong with the PATH.  I would have expected it to try to install in firemodels\FDS\FDS6.  We will have a look and let you know.

--

You received this message because you are subscribed to the Google Groups "FDS and Smokeview Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fds-smv+u...@googlegroups.com.
To post to this group, send email to fds...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/fds-smv/7154a4f7-45c7-495e-95b2-096f0dd27e08%40googlegroups.com.

[Glenn Forney]

the installer first unpacks files to a temporary directory then copies them to the final destination usually firemodels\FDS\FDS6 .  this lets the installer handle the case when you've already got files at firemodels\FDS\FDS6 more gracefully

open up a command shell and type set > env.out and send us the env.out file .  maybe there something different about your environment that we have not accounted for.

this is a long shot but try doing the install again. this time instead of typing yes - just hit the return key.  if this still doesn't work try answering no and answer all the following questions individually.

what type of system do you have - ie what version of windows are you running?

To view this discussion on the web visit https://groups.google.com/d/msgid/fds-smv/CAC6wax21PfKTkeabonRj-BWd8QY7WGh8SitjVTUKVdZkkOwcxg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Glenn Forney

[Salah Benkorichi]

Windows 10

By any chance, do you have either fds or smokeview open during the installation? 

Also, have you tried the option "no" and tried to install it elsewhere?

To view this discussion on the web visit https://groups.google.com/d/msgid/fds-smv/CA%2BGOW%2BJ4GjpSiR-vj39NYdQU9W9cS_pfC4H%3DM7cSKqKwrEp-%3DQ%40mail.gmail.com.

[C Irvine]

Apologies, on actually running a test it seems to be working fine with both fds 6.7.1 and smokeview 6.7.5 running normally. Not sure what the error was about. I'm running windows 10 pro.

Thanks for the quick responses as ever

[Glenn Forney]

thanks for reporting back.  let us know if you encounter any more problems.

To view this discussion on the web visit https://groups.google.com/d/msgid/fds-smv/a008c923-6090-4751-93fb-4e234f5df669%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Glenn Forney

[Glenn Forney]

the fds/smv bundle at the link below should fix the problem.  give it a try and let us know if it works for you.  even though fds and smokview are working your installation stopped a little short of where it should have.  The problem was that the "more" command which installer uses behaves a little differently on some windows systems (I'm guessing you have windows 10 enterprise ?).  Marcos found a work around (adding /E to the command) that works for us on our windows 10 enterprise system.

https://drive.google.com/drive/folders/0B_wB1pJL2bFQcURod1UyZTJUaEE?usp=sharing

To unsubscribe from this group and stop receiving emails from it, send an email to fds-smv+unsubscribe@googlegroups.com.

To post to this group, send email to fds...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fds-smv/a008c923-6090-4751-93fb-4e234f5df669%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Glenn Forney

[Stephen Olenick]

I can confirm I had the same issue described above by C Irvine.  Windows 10 Pro machine.  The official release installer gave the same error described above and the installation stopped short, but FDS did appear to still be working.  Nevertheless, the bundle at the link below that you provided installed cleanly.  Many thanks.

Stephen Olenick

Combustion Science & Engineering, Inc.

To view this discussion on the web visit https://groups.google.com/d/msgid/fds-smv/a008c923-6090-4751-93fb-4e234f5df669%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Glenn Forney

[Glenn Forney]

thanks for reporting.  the installer at the link you used is now on the "official" download site

To view this discussion on the web visit https://groups.google.com/d/msgid/fds-smv/e1286ddb-0ce4-4eff-8cf0-a1bec95bf53b%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Glenn Forney

[Mai]

Hi,

I came across a similar problem when trying to run FDS with Windows 10 enterprise.

The latest release FDS 6.7.1 SMV 6.7.5 doesn't show any error during installation, also uninstallation works fine.

But I am not able to successfully run the program using the new CMDfds while typing fds_local couch.fds

There is no reaction at all, no warning or error message, no message about reading the input file or anything else.

The old bundle FDS 6.7.1 SMV 6.7.4 is not installed correctly, and I am getting the same error message as C Irvine reported.

The older release FDS 6.7.0 SMV 6.7.1 is installed correctly and is executed correctly as well.

Do you have any ideas about what is going wrong?

Thanks a lot!

Mai

[dr_jfloyd]

Are you running in a directory that you have write permission for? (i.e. did you copy couch.fds to a folder under your user account?)

[Glenn Forney]

also, did you reboot your computer?

--
You received this message because you are subscribed to the Google Groups "FDS and Smokeview Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fds-smv+u...@googlegroups.com.
To post to this group, send email to fds...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/fds-smv/6a74d5d4-86c2-432d-b32a-0e6576bdb276%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Glenn Forney

[Mai]

Yes, I was running it on Desktop under my user account I have write permission for.
And yes, I tried to get it work without as well as with reboot. Previous releases were running smoothly without rebooting.

I tried another Windows 10 Enterprise computer on which even the release FDS 6.7.1, SMV 6.7.4 works nicely. It may have other firewall settings, e.g., I have to check.

But the installation messages didn't report any errors. Is it possible that execution is blocked by a firewall yet?

Many thanks!

Am Dienstag, 9. April 2019 16:55:35 UTC+2 schrieb Glenn Forney:

also, did you reboot your computer?

On Tue, Apr 9, 2019 at 10:50 AM dr_jfloyd <drjf...@gmail.com> wrote:

Are you running in a directory that you have write permission for? (i.e. did you copy couch.fds to a folder under your user account?)

On Tuesday, April 9, 2019 at 10:25:23 AM UTC-4, Mai wrote:

Hi,

I came across a similar problem when trying to run FDS with Windows 10 enterprise.

The latest release FDS 6.7.1 SMV 6.7.5 doesn't show any error during installation, also uninstallation works fine.

But I am not able to successfully run the program using the new CMDfds while typing fds_local couch.fds

There is no reaction at all, no warning or error message, no message about reading the input file or anything else.

The old bundle FDS 6.7.1 SMV 6.7.4 is not installed correctly, and I am getting the same error message as C Irvine reported.

The older release FDS 6.7.0 SMV 6.7.1 is installed correctly and is executed correctly as well.

Do you have any ideas about what is going wrong?

Thanks a lot!

Mai

--
You received this message because you are subscribed to the Google Groups "FDS and Smokeview Discussions" group.

To unsubscribe from this group and stop receiving emails from it, send an email to fds...@googlegroups.com.

To post to this group, send email to fds...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fds-smv/6a74d5d4-86c2-432d-b32a-0e6576bdb276%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Glenn Forney

[Mai]

Unfortunately, this issue is not resolved yet.

The following behavior occurs:
FDS 6.7.5 works on Win 10 (version 17.09), not on Win 10 (version 18.03). Installation doesn't show any error. Execution gives no reaction nor error message.

Some further observations may help or not:
2) Execution of all the .exe- and .bat-files works by typing (e.g.) "C:\Program Files\firemodels\FDS6\bin\background.exe", except "fds.exe" and "test_mpi.exe".
3) Double-clicking the file fds.exe in C:\Program Files\firemodels\FDS6\bin gives attached error message although this is path in my PATH.
4) Double-clicking the file fds.exe on the Win 10 computer results in the error message that impi.dll is not found although FDS is working fine

Do you have any further ideas that may help?
Does anyone have any experience running FDS on Win10 enterprise (18.03)?

Thank you very much for any help!

[fde]

Do you have space character in your Windows user name?

Do you run the installation exe of FDS as administrator?

[Mai]

Yes, I ran the installation file as administrator.

I do not have a space character in my user name.

Thanks for asking!
Are there any other suggestions?

[Glenn Forney]

did you do the following to run your case?

1. double click on CMDfds

2. fds_local casename.fds

double click on the CMDfds command shell that should have appeared on your desktop or is also in the start menu under FDS6

type where fds_local .  what does it say?

To unsubscribe from this group and stop receiving emails from it, send an email to fds-smv+u...@googlegroups.com.

To post to this group, send email to fds...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/fds-smv/605eb54d-4ca5-444d-aadd-3414babf4d4a%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Glenn Forney

[Mai]

Yes, I did these two steps to run the case.
I did the standard installation usually, but tried the costum installation, too. Same results.

Typing where fds_local gives the output

C:\Program Files\firemodels\FDS6\bin\fds_local.bat
Looks fine...

I am hoping that the IT in my company can install FDS on a fresh Win 10 enterprise (18.03). If it successful, our internal settings doesn't fit to some settings that came with the new CMDfds.
What else can I do?
Thanks a lot for any ideas!

To view this discussion on the web visit https://groups.google.com/d/msgid/fds-smv/605eb54d-4ca5-444d-aadd-3414babf4d4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Glenn Forney

[Glenn Forney]

Don't double click on fds.exe or fds_local.bat files. Double click on CMDfds icon . Then type in the window that opens up the following: 

fds_local casename.fds 

where casename.fds is the name of your input file

To unsubscribe from this group and stop receiving emails from it, send an email to fds-smv+u...@googlegroups.com.

To post to this group, send email to fds...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/fds-smv/e4406908-940a-4801-9b14-73c2b38fda47%40googlegroups.com.

[Mai]

The problem is resolved. The file mpiexe.exe was blocked by the internal firewall.