TV1 not generating all the point cloud

Problem:

While trying to process TV1 data in LP360, you may encounter an error where only a small section of the point cloud is generated, either the beginning or the end.

This error may also come with the following warning:

Check the following article, if the issue is related to: Trajectory File Time Range Warning article

The issue is related to the post-processed trajectory solution of SBET not matching the flight lines generated.
This means, that since the sbet does not match with the trajectory, the point cloud will be generated only on the areas where the sbet matches with the flight lines.

In the previous example, we can see that the point cloud is only available during the landing.

Possible resolution #1:

This problem may not have a solution, but we can try to identify what failed during the trajectory processing.

1. Open Trajectory Plot after performing trajectory processing, and check the quality of the solution. I recommend reading this article to understand more about the issue.
   If the trajectory solution is not good, you can stop at this point. Review the base station observation file (rinex). Check for gaps or anomalies in it.
2. If the trajectory solution is good. Mainly, all the trajectories are within Q1 result. Then we will review the INS processing.
   
3. In the trajectory plot, change the view from Gnd Trk to Accel. Check if the flight acceleration was constant or if there were changes. A normal plot should have changes during the alignment manoeuvres at the beginning and end of the mission.
   
4. Finally, we can check the starting time of the INS filter to compare it with the flight lines time. Go to --> <Project_folder>\Area_\Cycle_xxxxx\POS\TrajectoryProcessing_xxxx
5. Open the file xxxx_xxxxx_LP360InsFilter_LOG.txt --> Check for the line
   10:15:56.319 [INFO   ] [ 15176] Adjusted time interval 'after Heading Initialization' [s]: { 333142.200000, 333155.700000 }
6. These times represent the starting and ending GPS time of the sbet or post processed trajectory. You can compare these times to the raw trajectory. Go to Trajectory Processing --> Press "Override Range"
   

7. If we compare the starting and ending of the flight, to the start and ending of the sbet, we can see that only the landing part of the flight was processed.
   SBET time <333142 to 333155>
   Trajectory time <331417 to 333212>

   Where is the issue? How do I solve it?

   In this case, there is no solution. What happened is that the user did not perform the heading alignment maneuver at the beginning and ending of the flight to initialize the IMU of the sensor. This can be seen in the unusual acceleration of the sensor during the flight. Since there was no HAM, the heading value was never locked, and the INS filter never started.

   In this case, the user had a problem with the HAM, since it was missing and the dataset can not be recovered. The recommendation is to repeat the flight.