fds2ascii can't read FED slice

[sbenkorichi]

Glenn,
I was trying to extract output file from FED slice file with fds2ascii, but it doesn't show an option for it when I choose slices.
Could you please take a look when you get some time.
I attach a dummy file for it.
I also tried to use Output data to file in the Bound dialogue box, but nothing seems happening.
FED.fds.txt

[gforney]

I assume smokeview created the slice file not fds? If so, then why not use smokeview's option for outputting data from a slice file. otherwise you'll have to put the .smv entries that smokeveiw creates where fds2ascii wants to find them.

[sbenkorichi]

I simply copied fds2ascii to the case directory and run it from there. IT loads other slices but not FED slice.

[sbenkorichi]

Here

$ ./fds2ascii_linux_64 
  Enter Job ID string (CHID):
FED
  What type of file to parse?
  PL3D file? Enter 1
  SLCF file? Enter 2
  BNDF file? Enter 3
2
  Enter Sampling Factor for Data?
  (1 for all data, 2 for every other point, etc.)
1
  Domain selection:
    y - domain size is limited
    n - domain size is not limited
    z - domain size is not limited and z levels are offset
    ya, na or za - slice files are selected based on type and location.
        The y, n, z prefix are defined as before.  
n
  Enter starting and ending time for averaging (s)
0 40
  1  CARBON DIOXIDE VOLUME FRACTION  FED_01.sf
   slice bounds:     0.00     3.00     1.60     1.60     0.00     3.00
  2  CARBON MONOXIDE VOLUME FRACTION  FED_02.sf
   slice bounds:     0.00     3.00     1.60     1.60     0.00     3.00
  3  OXYGEN VOLUME FRACTION  FED_03.sf
   slice bounds:     0.00     3.00     1.60     1.60     0.00     3.00
 How many variables to read:

There is no 4th option for FED. Unless it's not intended to do that.

[gforney]

if the fed slice was not created by fds then fds2ascii will not know how to deal with it. I assume the fed slice was created by smokeview. I believe fds only creats fed quantities for devices. As I said in my earlier message, I bet that you can trick fds2ascii to deal with the fed slice by adding the smv like entries that smokview createds and add them by hand to the .smv file - just a guess though . I have never done this

[sbenkorichi]

Yes, you are right with point 1, fds only creates devices not slices. Either we should make fds output it as a slice directly, then use fds2ascii or we try your suggestion through smokeview.
@mcgratta
I would like to hear what Kevin would say about this.

[gforney]

I believe the reason why we didnt do a fed computation for a slice file this in the first place was that the fed integration requires past information (which required memory) to perform the integration. It was decided then to do this in smokeview. I think you can still do this in fds2ascii by adding the SLCF info for the fed files that smokeview generates to the .smv file

…

On Tue, Oct 10, 2017 at 5:02 PM, Salah Benkorichi ***@***.***> wrote: Yes, you are right with point 1, fds only creates devices not slices. Either we should make fds output it as a slice directly, then use fds2ascii or we try your suggestion through smokeview. @mcgratta <https://github.com/mcgratta> I would like to hear what Kevin would say about this. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5566 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AL1BRsoesIvu45BMYfr3NeC4K7XiuvRvks5sq9t5gaJpZM4P0ZQj> .

-- Glenn Forney

[sbenkorichi]

Thanks for the info.
I will try on your suggestion to see if I can get it working.

[sbenkorichi]

I was checking the commits, your last commit firemodels/smv@292d360 that was making this complain about libifcore.a library.
line 103 in makefile: INTEL_LIBS_LINUX =$(IFORT_COMPILER_LIB)/libifcore.a
If we're moving towards modules, then I believe we should provide explanation later on regarding how smokeview could be compiled.