Feature #1907
openfeatures for automated common lines
0%
Description
Hi Dmitry,
you wanted me to put down the things I've noted running automated common lines:
1. Final map name should have a date/project associated to it - makes it easier to keep track of which map was which
2. I like the idea to create and run it on a Template Stack. The disadvantage is that Templatestacks are Project and not Session related. This can cause confusion if you are running several sessions within one project - what do you think?
3. I think it is necessary to compare projections and related backprojections for each final result map - It would be really cool if one could go one step below that and see the projections and backprojections of the original maps that were later merged too - but that is not so important
4. Again not so important - Would it be possible to limit the number of classes that go into one map (before averaging?).
No data to display