questionable use of dbDir() in fileOperations::readObjects
Either a bug, or a misunderstanding:
In fileOperations::readObjects we have this code:
fileName path(db.path(instance, db.dbDir()/local));
If we follow through the hierarchy, this goes back to IOobject::path() with two parameters. There it has this code:
return rootPath()/caseName()/instance/db_.dbDir()/local;
This appears to be a doubled up use of dbDir.
Leads to this type of debug info:
fileOperation::readObjects : db:"<path>/cylinder-new/finite-area/region0" instance:"0"
fileOperation::filePath : fName:"<path>/cylinder-new/0/finite-area/finite-area"
when the raw registry has dbDir() = "finite-area/region0"
and the overloaded version has dbDir() = "finite-area"
Not sure why this just appears now...
Edited by Mark OLESEN