WEBVTT

00:00:00.040 --> 00:00:01.760
Hello, I'm Jeff Jalbrzikowski.

00:00:02.200 --> 00:00:06.270
In this video, we will discuss and demonstrate session processing

00:00:06.330 --> 00:00:07.400
in OPUS Projects.

00:00:09.680 --> 00:00:12.410
Please note, the current version of OPUS Projects may look

00:00:12.460 --> 00:00:14.440
slightly different than what we show here.

00:00:14.920 --> 00:00:17.680
The functionality generally remains the same.

00:00:20.880 --> 00:00:25.310
Before we move into the demonstration, let's consider our preprocessing

00:00:25.370 --> 00:00:27.120
checklist for your projects.

00:00:27.440 --> 00:00:30.780
Any marks with existing PIDs that are occupied should already

00:00:30.840 --> 00:00:33.360
be linked using the Upload description button.

00:00:34.800 --> 00:00:38.180
But recall that for this training, there are 4 marks

00:00:38.240 --> 00:00:40.320
with PIDs that we will not link.

00:00:40.760 --> 00:00:43.000
OK, we're going to treat those as new marks.

00:00:43.640 --> 00:00:46.990
Remember, don't link those noted on the right because there's

00:00:47.040 --> 00:00:48.800
no undo button in OPUS Projects.

00:00:50.640 --> 00:00:54.220
If you intend to follow along with subsequent modules that

00:00:54.280 --> 00:00:58.420
review session solutions and network adjustments, take a moment Now

00:00:58.480 --> 00:01:01.140
to ensure that you have the same 8 CORS in

00:01:01.200 --> 00:01:02.000
your project.

00:01:04.800 --> 00:01:06.360
We'll start here on the manager's page.

00:01:06.920 --> 00:01:09.319
Notice that there's no button to get to the Sessions

00:01:09.370 --> 00:01:09.600
page.

00:01:10.319 --> 00:01:14.730
What we do is we use these session names that

00:01:14.830 --> 00:01:19.440
are hyperlinks in the Marks and Sessions table.

00:01:22.640 --> 00:01:25.959
Each column of the Marks and Sessions table represents one

00:01:26.020 --> 00:01:26.480
session.

00:01:29.440 --> 00:01:32.700
Each session name in the header of the table functions

00:01:32.760 --> 00:01:35.720
as a hyperlink to navigate to that sessions page.

00:01:37.959 --> 00:01:41.050
Note the names are the year, the day of the

00:01:41.120 --> 00:01:44.709
year, followed by a letter code for the session in

00:01:44.790 --> 00:01:47.950
that day, A for the first, B for the second,

00:01:48.020 --> 00:01:49.960
C for the third, and so on.

00:01:52.360 --> 00:02:01.270
Let's navigate to the Sessions page for 2020 1041A by

00:02:01.440 --> 00:02:10.690
clicking on the hyperlink when the Sessions page loads.

00:02:11.650 --> 00:02:15.210
First note the similarity to the Managers page and the

00:02:15.280 --> 00:02:18.650
controls on the left and the Marks and CORS tables

00:02:18.710 --> 00:02:19.570
on the right.

00:02:21.010 --> 00:02:24.790
But also note the button that can quickly navigate you

00:02:24.860 --> 00:02:27.530
back to the Managers page when needed.

00:02:29.080 --> 00:02:32.040
If we scroll down, we see there are two tables

00:02:32.110 --> 00:02:34.360
below the map on the Sessions page.

00:02:35.200 --> 00:02:39.950
The Solution Quality Indicators table which summarizes statistics from the

00:02:40.010 --> 00:02:43.800
OPA solution reports of each mark occupied in this session.

00:02:45.919 --> 00:02:49.200
Below that table is the Data Availability table.

00:02:49.560 --> 00:02:51.790
This table is akin to the time-based view in

00:02:51.840 --> 00:02:53.080
some commercial software.

00:02:55.480 --> 00:02:59.480
If we scroll back up, we should notice the button

00:02:59.560 --> 00:03:01.280
to set up processing.

00:03:02.080 --> 00:03:03.960
Let's go ahead and click that button.

00:03:06.960 --> 00:03:11.020
Now that we're in the session processing window, we should

00:03:11.090 --> 00:03:14.800
take a look to see that OPUS Projects has recommended

00:03:14.870 --> 00:03:17.040
a single hub constrained in 3D.

00:03:17.720 --> 00:03:20.740
Here we see L O Y 2, or LOY2, has been

00:03:20.830 --> 00:03:22.560
our recommended hub.

00:03:23.440 --> 00:03:26.540
In this case, we'd like to keep the defaults for

00:03:26.610 --> 00:03:30.040
all the settings, so let's go ahead and click Perform

00:03:30.100 --> 00:03:34.560
Processing now that we've landed on the Processing queue confirmation

00:03:34.630 --> 00:03:35.080
window.

00:03:35.360 --> 00:03:38.430
Before closing this window, we may want to take note

00:03:38.490 --> 00:03:41.800
of the number of processing requests in the queue before

00:03:41.860 --> 00:03:42.160
ours.

00:03:43.760 --> 00:03:47.210
After we've checked that, we can go ahead and click

00:03:47.270 --> 00:03:47.680
close.

00:03:49.320 --> 00:03:53.550
A convenient way to move to the next session for processing

00:03:53.640 --> 00:03:58.130
is to click the drop down menu here, next to Session.

00:03:58.220 --> 00:04:01.920
Let's move over to 2021-041B.

00:04:07.710 --> 00:04:10.680
Note there's only one mark in this session, so there's

00:04:10.730 --> 00:04:12.270
not a whole lot to see here.

00:04:14.750 --> 00:04:16.589
Let's click the Setup Processing button.

00:04:17.589 --> 00:04:20.570
Now that we're in the session processing window for the

00:04:20.630 --> 00:04:23.610
next session, we could quickly check to ensure that the

00:04:23.670 --> 00:04:26.810
same hub was recommended for our constraint, which is what

00:04:26.870 --> 00:04:29.470
we want to do for the vast majority of projects.

00:04:30.279 --> 00:04:34.520
If not, we can use the check boxes to choose

00:04:34.620 --> 00:04:39.450
a different hub, and once we're ready, we go ahead

00:04:39.540 --> 00:04:42.920
and click Perform Processing again.

00:04:42.920 --> 00:04:45.529
Remember, this is your only chance to look at the

00:04:45.589 --> 00:04:48.790
number of processing requests in the queue before yours, and

00:04:48.839 --> 00:04:50.440
then go ahead and click close.

00:04:52.400 --> 00:04:54.700
As I work through the processing of the other four

00:04:54.740 --> 00:04:57.320
sessions in the background, I will mention a few things.

00:04:58.839 --> 00:05:02.549
Each session in OP is processed independently, so there's no

00:05:02.610 --> 00:05:05.760
need to wait for the first session solution to move

00:05:05.820 --> 00:05:07.920
on to the next session processing.

00:05:09.640 --> 00:05:13.190
When you land in the session processing window, briefly confirm

00:05:13.240 --> 00:05:15.890
that you've got a single hub selected and it is

00:05:15.940 --> 00:05:19.830
constrained in 3D, which refers to latitude, longitude, and ellipsoid

00:05:19.880 --> 00:05:20.279
height.

00:05:22.080 --> 00:05:25.820
A quick reminder, before closing the queue confirmation window, it

00:05:25.880 --> 00:05:28.320
is a good idea to check the time queued and

00:05:28.370 --> 00:05:31.040
the number of processing requests before yours.

00:05:31.839 --> 00:05:34.370
That window is the only place to check those items

00:05:34.420 --> 00:05:35.640
and they do not refresh.

00:05:38.080 --> 00:05:43.490
Once we've performed the session processing for all six sessions,

00:05:43.570 --> 00:05:47.980
we'll go ahead and click the Manager's page button to

00:05:48.070 --> 00:05:50.480
return to the manager's page.

00:05:54.279 --> 00:05:56.720
When we land back on the manager's page, the first

00:05:56.770 --> 00:05:59.600
thing you might notice that the processing vectors are now

00:05:59.650 --> 00:06:00.480
shown on the map.

00:06:01.520 --> 00:06:03.799
Let's click the Show Marks and CORS button.

00:06:08.600 --> 00:06:08.840
Now,

00:06:08.840 --> 00:06:12.960
from the manager's page, I can see that one session

00:06:13.040 --> 00:06:17.230
solution has been sent to the project at this point,

00:06:17.310 --> 00:06:21.510
annotated by the blue line in the Marks and Sessions

00:06:21.589 --> 00:06:26.430
table, which matches the symbology of the baselines drawn in

00:06:26.510 --> 00:06:27.160
the map.

00:06:32.040 --> 00:06:35.460
Now we can see that we've received solutions for all

00:06:35.529 --> 00:06:39.010
six sessions, as indicated by the blue line below the

00:06:39.080 --> 00:06:42.040
session name in the Marks and Sessions table.

00:06:43.160 --> 00:06:46.890
If we'd like to revisit the Sessions page for any

00:06:46.960 --> 00:06:51.300
given session, we just click again the hyperlink from the

00:06:51.380 --> 00:06:53.279
Marks and Sessions table.

00:06:55.920 --> 00:07:00.430
To reperform any of our session processing, we click the

00:07:00.510 --> 00:07:02.440
Setup Processing button.

00:07:03.520 --> 00:07:07.990
For example, if I'd like to try a different hub

00:07:08.080 --> 00:07:13.410
for some session processing, we would add to the current

00:07:13.500 --> 00:07:18.640
name, never delete the root name, and let's type LS03.

00:07:21.040 --> 00:07:27.490
We would switch our hub to LS03, change our constraint

00:07:27.610 --> 00:07:31.080
and click Perform Processing.

00:07:32.760 --> 00:07:39.120
Close the queue confirmation window, turn to the manager's page

00:07:39.220 --> 00:07:41.840
and wait for our solution.

00:07:43.280 --> 00:07:47.440
Now we can see our extra session with a different

00:07:47.530 --> 00:07:51.520
hub is now in our project, evidenced by the new

00:07:51.610 --> 00:07:56.280
column in the Marks and Sessions table and the presence

00:07:56.370 --> 00:08:00.280
of a lot more baselines shown in the map here.

00:08:02.480 --> 00:08:06.070
Now that we have this extra solution that we don't

00:08:06.140 --> 00:08:10.300
need, let's go ahead and click the Solutions button, which

00:08:10.380 --> 00:08:13.320
brings us to the Manage Solutions window.

00:08:14.680 --> 00:08:17.660
In this window, we can use the check boxes to

00:08:17.720 --> 00:08:21.300
delete any session solutions that we no longer want in

00:08:21.360 --> 00:08:22.160
the project.

00:08:23.800 --> 00:08:27.360
Don't forget to click the Apply Changes and close button

00:08:27.420 --> 00:08:28.760
to complete the task.

00:08:29.760 --> 00:08:30.680
Heed the warning.

00:08:32.600 --> 00:08:37.200
Click OK If your training project now looks like this,

00:08:37.290 --> 00:08:41.209
with six and only six solutions in the Marks and

00:08:41.290 --> 00:08:46.150
Sessions table on the Managers page, then you're ready to

00:08:46.240 --> 00:08:50.160
start reviewing all of your session solutions.

00:08:52.280 --> 00:08:56.819
This module was written and narrated by Jeff Jalbrzikowski and

00:08:56.890 --> 00:08:58.480
recorded in May 2024.

00:08:59.120 --> 00:09:03.400
For further information, please visit the OPUS Projects homepage.