The --sup-to-pdb-file and --sup-to-stdout options obliterate the chain codes of the input structures. This made a lot of sense when we only processed single-chain structures. But it's pretty messy if processing a multi-chain structure. In that context, the code should at least warn, but probably barf (with refs to other options - --sup-to-pdb-files).
I've gone for warning rather than barfing for now. In part because I'm concerned about the affect barfing could potentially have on Genome3D superpositions.
Following on from #68...
The
--sup-to-pdb-file
and--sup-to-stdout
options obliterate the chain codes of the input structures. This made a lot of sense when we only processed single-chain structures. But it's pretty messy if processing a multi-chain structure. In that context, the code should at least warn, but probably barf (with refs to other options ---sup-to-pdb-files
).