Changes to the Windows FDS command line functionality

[Kevin]

Starting with the latest release of FDS, 6.7.1, there is a change in how FDS is run at the command prompt under Windows. When you install the latest version of FDS, you will notice an icon that appears on your desktop that looks like the command prompt, but it is called CMDfds. Essentially, this is just a command prompt , but when it is opened, a few PATH variables are set that point to the location of the most recent FDS executables and libraries. We are doing this because we have had a number of complaints from users that they could not run parallel (MPI) simulations. The reason was usually confusion over which version of mpiexec to run, in particular when third-party apps like PyroSim had been installed. 

Now, when you open the CMDfds icon, you have the choice of either running FDS locally; that is, only on your own computer. You can still use OpenMP and MPI, but only your own computer's resources will be used. If you type 

helpfds

at the prompt, you can see the syntax of the command fds_local. If you want to run a simulation using multiple computers, you use the command mpiexec much as you did before. The difference between fds_local and mpiexec is that with fds_local, there is less chance of trouble involving networks, firewalls, and so on. 'fds_local' is really an alias for 'mpiexec -localonly'. 

There are more details in the FDS User's Guide. Even experienced FDS users should take a quick look and try out the two commands. Please let us know immediately if you run into trouble. You can post comments to this discussion group thread.

[fde]

Thank you for the description. 

1. When I try to run a single mesh local run which has a space in the file name I receive the following error (attached photo)
   
2. Is it possible to start in the directory of the shortcut of CMDfds? It is not convenient to go to the directory each time I run the CMDfds. 
3. Are the old commands are still valid? (fds filename.fds and mpiexec -localonly -n N fds filename.fds)

Thank you.

[Salah Benkorichi]

1. Try to avoid white space.

2. Might be possible but can be risky by changing the registry, so not recommended. You can simply Pin it on the Taskbar for quick access, just highlight the folder directory and type cd and click right to move quickly.

3. Yes, I tried it on a normal cmd and works fine. I usually on windows use ConEmu as I find it handy, you can get it from here https://conemu.github.io/

--
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/619a02c6-c646-4c64-b9ec-e1bb5a183573%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[fde]

1. Quotes are there for the space. But it does not work. Previously I could use quotes. 

2. Do you mean copying the folder location and pasting into the cmd window? I prefer clicking into the folder directory and type "cmd" and enter. Opening the command window starts in the current directory. 

3. I also checked and old commands still work. I hope they will not be absolute in future because it seems that I will prefer to stick with the previous commands. 

[Glenn Forney]

to change the directory the command shell short CMDfds opens up in

1. right click on CMDfds

2. click on the Properties menu item

3. click on shortcut tab

4. change the "Start in" field to the directory you want CMDfds to open up in

note, you make copies of the CMDfds short cut and have each copy open in a different directory

also note:  you can see in the Target field what CMDfds is doing - running the script fdsinit.  If  you want you could run fdsinit in a normal command shell

I do not recommend using spaces in file names.  I do not know about fds but spaces in filename will cause smokeview to break

[Naik]

Hi Guys,

I am getting error in running new version. See image below. Please help.

Regards,

Pramod

[dr_jfloyd]

Per the User's Guide and the first post in this thread the command is now fds_local if you wish to run a single process.

[Naik]

Working now.

thanks Dr

[blackarrow90]

I posted this in another topic, but it should be posted here. After installing the newest version of FDS I didn't get any desktop icon (nor I could find it anywhere on computer) and when I try to run single process, it always says that impi.dll is missing.

[blackarrow90]

After searching a little bit on internet, I decided to copy all files from mpi folder to bin folder. FDS works now, but this is not actually a solution for the problem.

[Kevin]

If the CMDfds icon is not on the Desktop, it should be in the programs menu under FDS6, along with the manuals. Also, if you type CMDfds into the "Search Programs and Files" box, you should find it there too.

[blackarrow90]

No, it is not is this folder. Also, when I type it in search box, I can't find it.

[Kevin McGrattan]

How about

where mpiexec

--

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/4c9f919b-3b91-447c-98b0-9aae24f5680c%40googlegroups.com.

[Glenn Forney]

what version of windows are you using

[blackarrow90]

program files/firemodels/fds6/bin/mpiexec.exe

Windows 10 Pro

[Glenn Forney]

that is what I have on my home computer and I was able to install successfully.  Something must have gone wrong with your install. I suggest you install again

--

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/82cc9e70-4153-4962-935b-ea70eba4eba3%40googlegroups.com.

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

--

Glenn Forney

[blackarrow90]

I reinstalled the program, but it don't have the icon. However, I am not concerned about the icon than much. What bothers me is that FDS doesn't work at all and gives me message impi.dll missing, until I copy all files from bin/mpi to bin folder itself. Then it works fine.

[Salah Benkorichi]

I've requested you to share a screenshot of how it's getting installed. There might be something wrong poping up and you're not sorting it. 

To view this discussion on the web visit https://groups.google.com/d/msgid/fds-smv/c9c3ed6d-c60e-4ad3-8aa8-316ea8c265d1%40googlegroups.com.

[blackarrow90]

This is what I have:

[Glenn Forney]

one last thing to try.  run the installer again.  after it is finished reboot your computer.  Sometimes changes to  your path (which the installer is making) are not applied until after a reboot.  

[blackarrow90]

I always reboot after installation, however this is not the solution.

[fde]

Maybe you already followed the same steps but I would suggest: 

• uninstalling everything
• making sure no Intel MPI Hydra service is running
• making sure all MPI and FDS files are removed in the directory
• making sure no PATH variable is left regarding FDS and MPI Hydra
• Restarting the PC
• Then running the FDS setup as Administrator.