Menu

#170 pyFoamCompareDictionary.py option --not-equal

new
nobody
None
normal
trivial
always
none
A Utility
general
2013-03-30
2013-03-29
code-red
No

The --not-equal option of pyFoamCompareDictionary seems to be without effect. The output of pyFoamCompareDictionary is identical in these cases:

* I compare the the same dictionary of two different cases

Œ pyFoamCompareDictionary.py case01/system/fvSolution case02/system/fvSolution
Œ pyFoamCompareDictionary.py case01/system/fvSolution case02/system/fvSolution --not-equal

* I compare different dictionaries ot two different cases

Œ pyFoamCompareDictionary.py case01/system/fvSchemes case02/system/fvSolution
Œ pyFoamCompareDictionary.py case01/system/fvSchemes case02/system/fvSolution --not-equal

* Only, omitting the name of the second dictionary and passing the option leads to an error

Œ pyFoamCompareDictionary.py case01/system/fvSolution case02/ --not-equal

Is this the intended behaviour of this option?

Discussion

  • code-red

    code-red - 2013-03-29

    Sorry, I forgot to add my pyFoam version: 0.5.7

     
  • Bernhard Gschaider

    What is the behaviour that you're expecting?

    To quote from the online help
    {{{
    --not-equalŒŒŒŒŒŒŒŒŒŒŒŒ Allow source and destination to have different names
    }}}
    It says ALLOW, not REQUIRE

    Usual behaviour of the utlitiy is to only compare a fvSolution to a fvSolution (it will complain if the names are not the same). That switch allows you to compare a fvSolution to a fvSolution.safe. The disadvantage is that it will no longer look for the "soulmate" automagically. That was the error you were seeing.

    If you have a suggestion to the wording of the online help that explains it better (but still briefly): Please

     
  • code-red

    code-red - 2013-03-30

    If I compare different dictionaries of two different cases

    Œ pyFoamCompareDictionary.py case01/system/fvSchemes case02/system/fvSolution
    Œ pyFoamCompareDictionary.py case01/system/fvSchemes case02/system/fvSolution --not-equal

    then the output is exactly the same, whether I allow different names or not.

    I expected some kind of warning message. However, maybe stating the filename of the second dictionary overrides the assumption of equal filenames.

    By the way, I like the expression automagical.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.