case.ep written to mesh directory

[RobertM]

Running ElmerSolver from the terminal I'm confused about controlling the write-to location for the results file.

When my .sif file header looks like this:

Code: Select all

Header
  CHECK KEYWORDS Warn
  Mesh DB "." "hex_test_02"
  Include Path ""
  Results Directory ""
End

or this:

Code: Select all

Header
  CHECK KEYWORDS Warn
  Mesh DB "." "hex_test_02"
!  Include Path ""
!  Results Directory ""
End

the "case.ep" file is written to the /hex_test_02 directory, where the mesh.* files reside.

If the .sif header looks like this:

Code: Select all

Header
  CHECK KEYWORDS Warn
  Mesh DB "." "."
  Include Path ""
  Results Directory ""
End

then the mesh.* files need to be in the parent directory, which is where the case.ep file is written to.

From the my reading I did not think this was the expected behavior.

[annier]

Hi RobertM,
If you want to output the case.ep file in the mesh files directory, you can write like this:

Code: Select all

    Header
      CHECK KEYWORDS Warn
      Mesh DB "." "hex_test_02"
      Include Path ""
      Results Directory "."
    End

provided that the mesh files are within the hex_test_02/ directory. Please note that the hex_test_02 directory is within the parent directory.


Similarly, if you want to output the case.ep file outside the parent directory, the mesh files should be in the parent directory and then you can write like this:

Code: Select all

    Header
      CHECK KEYWORDS Warn
      Mesh DB "." "."
      Include Path ""
      Results Directory "../"
    End

Yours Sincerely
Anil Kunwar

[RobertM]

Anil:

Thank you for your quick reply, but I am not seeing the expected behavior:

With this header:

Code: Select all

Header
  CHECK KEYWORDS Warn
  Mesh DB "." "hex_test_02"
  Include Path ""
  Results Directory "."
End

and the mesh.* files in the hex_test_02 sub directory, the case file is written into the hex_test_02 subdirectory.

I've tried this running ElmerSolver 8.0 in a Lubuntu 15.04 VirtualBox Guest on a Windows 7 host, and also in a pre-packaged Elmer VDI (Ubuntu 12.04.3), again on a Windows 7 host.

It's not really a major problem, but it is confusing me.

Thank you again for your prompt reply.

Robert Milgate

[annier]

Hi Robert,
I informed you incorrectly in the previous post (updated/corrected).
In my context,i found the following results
Case I
when the mesh files are in hex_test_02 directory,

Code: Select all

Header
     CHECK KEYWORDS Warn
      Mesh DB "." "hex_test_02"
      Include Path ""
      Results Directory "."
   End

or,

Code: Select all

Header
     CHECK KEYWORDS Warn
      Mesh DB "." "hex_test_02"
      Include Path ""
      Results Directory ""
   End

give the same result. That is the case.ep is output into the hex_test_02 directory.

Case Ii
When all the mesh files are in the parent directory, named directory_1,

Code: Select all

Header
     CHECK KEYWORDS Warn
      Mesh DB "." "."
      Include Path ""
      Results Directory "."
   End

or

Code: Select all

Header
     CHECK KEYWORDS Warn
      Mesh DB "." "."
      Include Path ""
      Results Directory ""
   End

outputs the case.ep file in the same parent directory directory_1.

And,

Code: Select all

Header
     CHECK KEYWORDS Warn
      Mesh DB "." "."
      Include Path ""
      Results Directory "../"
   End

outputs the case.ep outside the parent directory directory_1.

the inference for this may be :
If the mesh file directory is present, the output file is by default written ito the mesh file directory/folder.
When the mesh file directory is not defined, then the Results "" command is used to define the path of the output case.ep file.

Yours Sincerely
Anil Kunwar

[RobertM]

Anil;

Thank you again for you reply, and also for confirming the behavior I am seeing.

I had a vague memory of running Elmer sometime in the past and having the case file written to the parent while the mesh files were in a sub-directory, and was expecting this. In retrospect, this behavior is more logical, as it associates the case file with the appropriate mesh, for some reason it just wasn't what I expected.

So, thank you again.

Robert Milgate