BUG : foamToEnsight -nodeValues places an extra space in the .case file

When the -nodeValues option is used in foamToEnsight, it places an extra space in the .case file for each variable (see attached pic).

This causes ensight to fail when trying to open the case. There is no issue when -nodeValues isn't used.

Changed title: foamToEnsight -nodeValues places an extra space in the .case file → BUG : foamToEnsight -nodeValues places an extra space in the .case file

By Justin Graupman on 2016-11-18T17:22:46 (imported from GitLab project)

Thank you for the information. I believe that it tested successfully with ens_checker, but will now to recheck with ensight too.

@graups : I guess that I should have asked which version or branch you are using. The develop branch (to be used for the upcoming 1612), plain 1606, or master? Examining the 1606 and master, I can see where the extra space comes from. In the develop branch, the Ensight infrastructure has been largely revamped and this particular problem shouldn't appear. Would you have time to check that the develop branch is fit for your purpose?

Since you are using Ensight, the develop branch (upcoming 1612) might interest you also for the addition of an ensightWrite function object.

@mark : I am using the develop branch, just an older revision prior to the latest foundation merge. The commit level I'm at is 57a1e6d2 from October 24th. If this has been fixed since then, then the develop branch is fit for my purposes. I will have to peek at the ensightWrite function object, I wasn't aware of it. Thanks!

By Justin Graupman on 2016-11-21T14:56:34 (imported from GitLab project)

Hi Justin, it looks like you only missed out by a few days. The ensight changes (3bdf6078b93) not much more than a week later (Nov 3). This also when the ensightWriter came in.

@mark : Thanks, I did update to the latest commit and test and this issue is indeed already fixed.

However, I did find another issue related to the foamToEnsight update ( Issue #317 (closed) ). Can you take a look at it?

You may close this report.

By Justin Graupman on 2016-11-28T23:05:45 (imported from GitLab project)

Status changed to closed