RC 1.2.2.116899 - Merge using overlaps / Broken component workflow

General Feedback & Requests
, ,
1

Hi everyone,
It looks like the procedure for merging components using “feature overlap” does not work anymore in 1.2.2

Usual procedure :
Dataset 1 and dataset 2 are overlapping (some images from dataset 1 are in dataset 2)
Steps :

  • Import and align dataset 1 in RC instance 1
  • Import and align dataset 2 in RC instance 2
  • [from instance 2] Export component C
  • [in instance 1] Import same component C
  • [in instance 1] Select all images and set feature source to “merge using overlaps”
  • [in instance 1] “Merge components”
    1.2.1 result : ultrafast merge, no additional feature detection
    1.2.2 result : on instance 1, feature detection for dataset 2, and a considerably slower process.

This is what really allows large datasets processing, so this is worrisome.

Anyone else having the issue ?
Thanks

2

Hi Iconem,
have you deleted the cache when you changed the RC’s versions?

3

Yes, I made sure of that.
I also previously tried to make a RC “clean install” reset with no luck.

4

Thank you for noticing this. I created a bug with this issue for our developers.

5

Please also note that the whole alignment process seems to have slowed down.
I currently am monitoring a merge of components that has been taking more than 15 hours. Merge using feature overlaps has never taken more than a few hours with previous versions.

6

It is possible that it will be connected with that bug, as features are again searched.

7

Feature detection takes more time yes, but the “processing” part seems to take a lot more time too.
In the 15 hours, feature detection has taken maybe 2 hours (instead of ~0) and other steps ~13 hours (instead of ~3)

8

It is strange. In my tests the times were similar. It shouldn’t take so much time. There could be also some other issue. The separate components were aligned in normal time?

9

When aligning the “regular way”, just getting chunks to merge later, the process times do not seem longer than usual.
But the weird 15-hrs alignment of last night is an attempt to merge components that are themselves the result of a merge.

Do you want me to setup some tests ?

10

During that 15 hours time what was the longest process in console view?
Where are your data saved? Is it local disc?

11

Longest process : I can’t say. It was during the night and the RC log is not timecoded (maybe some nice & easy feature to add). After 15 hours it was at 29% of the “processing” step. I understood it would be a lot more time before I got results, so I aborted the process and… downgraded to 1.2.1 to do it all again from scratch.

Data is on a network disk (always have). Cache is on local nvme disk.

12

Hello,

Is there any new release with a bug fix ?
Can I use an older version? (where to download ?)

Thanks
Ben

13

Hi Bennyman33,
for now there is no fixed version, but we are working on it.
The previous releases you can find on My - Sign in - Capturing Reality in Downloads section.

1 Like