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?
Sorry, I forgot to add my pyFoam version: 0.5.7
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
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.