Hello again. Thanks, Kevin, for your insights and helpful suggestions. I’m unfamiliar with command line structure, was barely able to get openMVG compiled in Visual Studio 2015, much less figuring out the workflow front to end. If you think otherwise and can point me to resources or tuts, I’m all ears.
I’ve been waiting to respond, was hoping to report a successful outcome to my strategy of activating only those camera poses on one side of the wall for one reconstruction, then the converse for the tunnel just on the other side of this sharp divide. This worked for the one side, but not for the other. Since, as you point out, RC operates under sequential SfM, the images falling on side A of the divide come earlier in the image sequence, which I though might explain why side A ran just fine. But, when I deactivated side A images and activated side B, I got the invalid function call again. I then deactivated incrementally more images on the front end of the sequence I thought might be the culprit(s), but no go. I then cleared cache, still no go. I then tried Götz’ idea, select side B camera poses and export XMP Metadata. These dropped into a new project with cleared cache, noted the georeference icon on some of the images, ran alignment and now RC crashes every time. Here’s the window it presents, but note in the console behind, WARNING: some calibration groups contain conflicting priors:
I can run this batch of images completely separately, but then face the dubious task of scaling and aligning for (next to) invisible seams. I’m truly out of ideas how to deliver this scene in its entirety into a common scale and coordinate system.