...
This is a special parameter that only applies if your panorama is not a full 360 degree panorama. In this case, the panorama motor has to guess the center of the first and the last image so the final result will have the desired angle. To do so, it needs to know the horizontal angle of the field of view the camera is set to.
North deviation
If this value is set to 0 (zero), the natural home position of the camera will be treated as facing north when calculating the parking position. In case the camera is not mounted facing north, this value must be set to the angle relative to north in degrees.
...
If you enable weather based parking then the camera will calculate its next parking position based on the current weather around her. it. For example, it will attempt to park facing away from the wind to protect its front glass from rain or snow. In order for this to work as intended it is crucial that the location and the north deviation are properly configured in the settings.
...
Depending on where the camera is mounted it can be beneficial to define a fixed parking position instead of parking based on the weather. Rule of thumb: Set a fixed parking position if the camera is mounted on or close to a wall and let her it face the wall when inactive. For freestanding cameras weather based parking will normally be the better choice.
...
Unified color temperature throughout a panorama can be tricky if there are multiple light sources around, since the camera might apply different color corrections for different images that then get stitched together into a single one. The panocam therefore calculates its own color temperature correction based on the first image in the panorama, and then applies these settings consistently to each individual image. The color temperature bias settings give you an opportunity to influence the result of that correction. You can adjust different biases for day and night, and the panocam will attempt to smoothly interpolate from one into the other at dawn or dusk.
Panorama stitching instruction
The required instruction file for the panorama stitching is generated automatically. This is done with the first batch of images captured by the camera.
Whenever there is a change of the image ( e.g. change of image size) or the camera position it is required to re-generate the stitching instructions.
...
This can be done in the event log, by expanding the latest PanoramaStitchingEvent (which is marked as an error because of a image size configuration change) and clicking on the yellow Regenerate stitching button.
Create a customized panorama stitching instruction (optional)
Besides the automatic panorama project generation, there is an option to upload a customized instruction file.
PanoCam uses the Hugin toolchain to stitch individual images together into one final panorama. To do so properly, it needs a project file that defines the properties and operations to be applied, so you'll have to create one and then upload it. However, there's a bit of a catch here: To create a Hugin project, you need to have the individual images the panorama consists of. Thankfully, the yellow portal provides you with an easy access to those images.
...
When doing that process, the product you're really interested in is not the stitched image, but the .pto file that hugin will ask you to save before creating it. Once you have that, you can use the file upload dialog in the panorama configuration on the yellow portal to upload it, and it will be applied to future panoramas taken by this camera. You may replace this project at any time you like if you come up with a configuration you like better.Important: As long as you do not upload a stitching project, the stitching will always fail. This is normal behaviour.