WEBVTT 00:00:01.000 --> 00:00:03.120 Hello and welcome to OPUS Projects Training. 00:00:03.720 --> 00:00:04.559 I'm Dan Martin. 00:00:05.519 --> 00:00:08.560 This video shows an overview of the OPUS Projects workflow. 00:00:09.240 --> 00:00:11.920 It is meant to be an introduction to the workflow 00:00:11.970 --> 00:00:15.190 and help you understand how topics covered in the following 00:00:15.250 --> 00:00:17.160 videos fit into the bigger process. 00:00:18.280 --> 00:00:20.920 Please note the current version of OPUS Projects may look 00:00:20.960 --> 00:00:23.600 slightly different than the screens in this presentation. 00:00:24.000 --> 00:00:26.480 However, the functionality generally remains the same. 00:00:30.040 --> 00:00:33.040 The first step is to create a project from the 00:00:33.110 --> 00:00:33.960 NGS homepage. 00:00:33.960 --> 00:00:39.280 We'll select OPUS Projects and we'll select Create. 00:00:41.880 --> 00:00:43.320 I'll enter my e-mail address. 00:00:48.900 --> 00:00:52.940 I'm going to skip the tracking ID in the Data 00:00:53.030 --> 00:00:54.740 Code project title. 00:00:54.740 --> 00:01:02.340 I'm going to leave the agency set to Not Defined. 00:01:02.960 --> 00:01:06.580 From the map, I can select the location of the 00:01:06.660 --> 00:01:10.740 project, or I could type in a latitude and longitude 00:01:10.819 --> 00:01:14.520 close enough and put in anticipated start date. 00:01:14.520 --> 00:01:18.140 Let's select today, and let's say we're going to have 00:01:18.209 --> 00:01:21.980 seven stations and the duration of the project will be, 00:01:22.040 --> 00:01:23.480 let's say, five days. 00:01:23.680 --> 00:01:25.160 Let's go ahead and create this project. 00:01:29.080 --> 00:01:32.850 So in here, you'll see the information, you'll see who 00:01:32.920 --> 00:01:36.980 the project manager is in the e-mail, the project keyword, 00:01:37.050 --> 00:01:40.680 meaning that's how you'll get in there when you want 00:01:40.750 --> 00:01:42.360 to access your project. 00:01:43.319 --> 00:01:44.959 The next thing we can do is go directly to 00:01:44.990 --> 00:01:46.240 the manager's page to this link. 00:01:54.580 --> 00:01:58.060 Once you're in the manager's page, we're going to select 00:01:58.130 --> 00:01:59.620 our project preferences. 00:02:00.900 --> 00:02:03.320 And in here, if you wanted to, you can change 00:02:03.370 --> 00:02:06.220 the project ID, the manager keyword, session keyword. 00:02:06.960 --> 00:02:08.770 For now, we're going to leave them just as they 00:02:08.810 --> 00:02:08.960 are. 00:02:10.919 --> 00:02:14.360 Now that we have our project created, we can upload 00:02:14.430 --> 00:02:15.240 RINEX data. 00:02:15.639 --> 00:02:17.000 There are two ways we can do this. 00:02:17.000 --> 00:02:19.510 One would be to use the add marks on the 00:02:19.570 --> 00:02:21.960 right hand side of the manager's page. 00:02:22.480 --> 00:02:27.000 Doing this will replace this window with the OPUS project's 00:02:27.080 --> 00:02:28.000 upload page. 00:02:28.360 --> 00:02:33.000 The other option would be to go right to the 00:02:33.110 --> 00:02:37.440 NGS web page and select OPUS and to do it 00:02:37.540 --> 00:02:38.600 from here. 00:02:39.560 --> 00:02:43.980 So let's choose our RINEX file, go back to our 00:02:44.070 --> 00:02:49.930 directory, let's select RINEX, and let's select the first day 00:02:50.020 --> 00:02:51.560 of observations. 00:02:52.200 --> 00:02:57.139 And let's select this file for 863F and we'll click 00:02:57.240 --> 00:02:57.720 open. 00:02:59.600 --> 00:03:03.580 The next thing to do would be to determine which 00:03:03.669 --> 00:03:07.320 antenna model it is and also what the HI is. 00:03:07.320 --> 00:03:13.360 The only way or the best way to do this 00:03:13.520 --> 00:03:21.110 would be to consult the field log, which tells us 00:03:21.260 --> 00:03:28.079 that the HI was 1.9991 and the antenna was a 00:03:28.240 --> 00:03:31.800 Trimble 115000 Dash 00. 00:03:33.160 --> 00:03:36.320 So let's minimize this 1.9991. 00:03:37.320 --> 00:03:42.980 Let's put an HI in of 1.9991 and antenna type TRM 00:03:43.100 --> 00:03:47.200 because we know there's a Trimble. 00:03:47.720 --> 00:03:51.120 And let's pick the 115000 None. 00:03:51.160 --> 00:03:52.760 None, meaning that there's no radome. 00:03:54.560 --> 00:03:57.940 Let's go to our e-mail address and then we go 00:03:58.020 --> 00:04:01.550 to Options and we're going to want to send this 00:04:01.620 --> 00:04:02.600 to a project. 00:04:02.600 --> 00:04:04.360 So we need to get our project identifier. 00:04:04.880 --> 00:04:08.120 Our project identifier would be in our e-mail. 00:04:09.360 --> 00:04:13.780 So I can simply copy the project ID from my 00:04:13.880 --> 00:04:19.120 e-mail and paste it here and then upload to static. 00:04:20.640 --> 00:04:23.080 So we can see that the file is uploaded. 00:04:23.279 --> 00:04:26.320 And at the bottom right, you can see that has 00:04:26.380 --> 00:04:27.800 gone to this project. 00:04:28.320 --> 00:04:30.680 Then we'd go back to the OPUS upload page and 00:04:30.740 --> 00:04:33.210 continue to upload the data for the rest of our 00:04:33.260 --> 00:04:33.680 project. 00:04:35.000 --> 00:04:37.839 So now that all of the RINEX files have been 00:04:37.910 --> 00:04:41.060 uploaded to our project, we would go in, review the 00:04:41.120 --> 00:04:44.400 uploads, look to make sure that there were no issues. 00:04:44.720 --> 00:04:46.560 For now, we'll just move on with the next step. 00:04:47.600 --> 00:04:50.470 So once we've checked our data, we're going to go 00:04:50.520 --> 00:04:52.279 ahead and upload descriptions. 00:04:52.960 --> 00:04:58.200 So I'm going to select the Upload description tab and 00:04:58.300 --> 00:05:02.160 we have 5 files that we need to upload. 00:05:02.839 --> 00:05:05.320 So we have a dot DSC file. 00:05:05.600 --> 00:05:08.540 Let's go back to our ODU directory, go to our 00:05:08.610 --> 00:05:11.680 descriptions and let's select the dot DSC file. 00:05:15.360 --> 00:05:24.890 Let's select the DES file, the error file. 00:05:33.360 --> 00:05:40.060 The discrepancy file and the neighbor file, and these are 00:05:40.180 --> 00:05:45.460 all the files that would have come out of the 00:05:45.580 --> 00:05:52.279 WinDesc software that we used to create our descriptions. 00:05:52.600 --> 00:05:56.870 Once those are all selected, we'd click upload Description and 00:05:56.940 --> 00:05:59.760 this will take just a moment to complete. 00:06:01.720 --> 00:06:05.380 And that's completed and there's no errors if I'm up, 00:06:05.440 --> 00:06:06.480 so that's good. 00:06:07.200 --> 00:06:09.400 Let's close this next. 00:06:09.400 --> 00:06:11.150 We're going to want to go in and upload our 00:06:11.190 --> 00:06:11.480 photos. 00:06:11.920 --> 00:06:15.020 So the way to upload our photos is to go 00:06:15.089 --> 00:06:16.640 to individual marks. 00:06:16.640 --> 00:06:19.750 Let's just go ahead and select GP 99 and we're 00:06:19.820 --> 00:06:24.080 going to see now that we've loaded our description information, 00:06:24.140 --> 00:06:28.540 the description information from our file has now been populated, 00:06:28.600 --> 00:06:31.240 but you can see that there's no photos. 00:06:31.240 --> 00:06:36.029 So let's select our photos and we have three photos, 00:06:36.130 --> 00:06:40.000 a close up, an eye level and horizon view. 00:06:40.240 --> 00:06:44.529 So let's select our close up and go back to 00:06:44.630 --> 00:06:48.120 our ODU and let's go to our photos. 00:06:48.720 --> 00:06:55.950 And let's go to GP 99 and let's select our 00:06:56.130 --> 00:07:04.570 close up and mark from high level and our horizon 00:07:04.740 --> 00:07:05.600 file. 00:07:07.200 --> 00:07:08.880 It looks like we have a few to choose from. 00:07:08.880 --> 00:07:14.030 Let's go ahead and pick this one and let's upload 00:07:14.140 --> 00:07:15.400 those files. 00:07:23.720 --> 00:07:25.450 And you can see now that those photos have been 00:07:25.490 --> 00:07:26.520 uploaded to the description. 00:07:26.640 --> 00:07:30.970 OK, so let's go ahead and go back to the 00:07:31.080 --> 00:07:32.600 managers page. 00:07:34.760 --> 00:07:36.800 And the next step we would want to do would 00:07:36.840 --> 00:07:38.360 be to select the distinct CORS. 00:07:38.360 --> 00:07:43.340 This is the CORS that will be used for atmospheric 00:07:43.440 --> 00:07:49.300 corrections, and it comes from somewhere between 375 and 800 00:07:49.400 --> 00:07:50.960 kilometers away. 00:07:51.320 --> 00:07:53.400 So let's go to the add delete CORS. 00:07:53.600 --> 00:07:56.180 You'll see a map will come up and originally be 00:07:56.240 --> 00:07:57.720 zoomed to our project area. 00:07:58.560 --> 00:08:00.360 But you can see we can select any of the 00:08:00.410 --> 00:08:00.680 CORS. 00:08:00.920 --> 00:08:03.680 And again, in each module following this or each video 00:08:03.730 --> 00:08:07.000 following this, there'll be further explanation in each of these 00:08:07.050 --> 00:08:07.360 steps. 00:08:07.360 --> 00:08:10.360 But for now, I know the station that I want 00:08:10.430 --> 00:08:11.480 to add is ASUB. 00:08:12.120 --> 00:08:13.880 I'm going to just going to put that right in 00:08:13.920 --> 00:08:14.240 the box. 00:08:14.240 --> 00:08:16.880 I could have selected it from the map, but we'll 00:08:16.940 --> 00:08:19.470 select it from the box and I'll click the Add, 00:08:19.520 --> 00:08:20.240 Delete CORS. 00:08:21.280 --> 00:08:24.970 The manager's page should refresh and now we can see 00:08:25.040 --> 00:08:28.170 that ASUB has been added to the list of core 00:08:28.240 --> 00:08:28.880 stations. 00:08:29.840 --> 00:08:32.360 Now that we're at this point, we can go ahead 00:08:32.420 --> 00:08:34.880 and select our first session for processing. 00:08:36.679 --> 00:08:38.690 I could come down and look and make sure that 00:08:38.740 --> 00:08:40.880 all the data coverage looks good, which it does. 00:08:41.360 --> 00:08:43.760 I'm going to go ahead and select Set Up Processing. 00:08:44.679 --> 00:08:49.840 By default, OPUS Projects has selected probably the most central 00:08:49.920 --> 00:08:54.250 CORS to my project as the hub station and everything 00:08:54.340 --> 00:08:58.179 looks the way that it should, and we're going to 00:08:58.260 --> 00:09:02.600 select Perform Processing that will quickly get done. 00:09:02.600 --> 00:09:06.340 It shows that there are 13 unconstrained and one constrained 00:09:06.410 --> 00:09:07.280 marks in this. 00:09:08.040 --> 00:09:11.010 There are no marks in the queue, so which means 00:09:11.070 --> 00:09:13.280 it should come back pretty quickly. 00:09:14.200 --> 00:09:16.860 We'll go ahead and close this and if we want 00:09:16.920 --> 00:09:20.429 to, we could continue to process our sessions by selecting 00:09:20.500 --> 00:09:21.040 the next. 00:09:21.160 --> 00:09:24.400 And then we continue to follow that process of setting 00:09:24.460 --> 00:09:28.059 up, processing, running all of the sessions through until we 00:09:28.120 --> 00:09:28.720 were done. 00:09:30.000 --> 00:09:32.740 So as you can see, we finished processing all of 00:09:32.800 --> 00:09:35.990 our sessions now and that's represented by the fact that 00:09:36.050 --> 00:09:38.559 we have vectors drawn from our hub to all of 00:09:38.620 --> 00:09:41.360 our station marks as well as to the other CORS. 00:09:43.360 --> 00:09:46.309 Normally, we would go in, check all of the quality 00:09:46.370 --> 00:09:49.679 indicators for each of these sessions, look to make sure 00:09:49.740 --> 00:09:53.280 that there was agreement between sessions on the same marks. 00:09:54.000 --> 00:09:57.000 But for now, we'll just go ahead and continue on 00:09:57.059 --> 00:09:58.119 with the process. 00:09:59.600 --> 00:10:02.710 So at this point, if I have real time data 00:10:02.780 --> 00:10:07.000 or GVX right, GNSS vector exchange format data, I'm going 00:10:07.080 --> 00:10:11.000 to go ahead and select that information, which we do. 00:10:13.559 --> 00:10:16.540 I'm going to browse for the GVX data. 00:10:21.640 --> 00:10:25.210 We'll select our GVX file and we'll open that and it comes 00:10:25.210 --> 00:10:28.690 in, it says that there are 15 vectors in this 00:10:28.790 --> 00:10:30.370 file and I'm going to go ahead and upload that 00:10:30.470 --> 00:10:31.960 to the project. 00:10:32.400 --> 00:10:35.380 And now you can see the purple dashed lines which 00:10:35.440 --> 00:10:37.080 represent the GNSS vectors. 00:10:38.480 --> 00:10:41.650 We would want to go in, check the GNSS vectors 00:10:41.720 --> 00:10:45.310 for any problems or errors, but finding none in this 00:10:45.380 --> 00:10:45.720 case. 00:10:45.720 --> 00:10:47.440 We'll continue on with our processing. 00:10:48.559 --> 00:10:51.000 The next step would be to run a preliminary adjustment. 00:10:51.520 --> 00:10:54.870 So we'll go over to set up adjustments, and you 00:10:54.940 --> 00:10:58.860 can see that there are these five adjustments that will 00:10:58.929 --> 00:11:00.360 be done in sequence. 00:11:00.360 --> 00:11:03.230 The 1st is preliminary, so I'm going to select each 00:11:03.290 --> 00:11:06.380 of my sessions that were processed, move them over into 00:11:06.440 --> 00:11:07.679 the included sessions. 00:11:11.559 --> 00:11:15.559 I'm going to want to make sure that my hub 00:11:15.660 --> 00:11:20.990 station in this case is selected as the constraint which 00:11:21.090 --> 00:11:26.040 was LOI 2, constrain that 3D and perform adjustment. 00:11:27.520 --> 00:11:30.860 And just like session processing, we'll get a splash screen 00:11:30.920 --> 00:11:33.980 that pops up that shows us some information about what 00:11:34.030 --> 00:11:37.210 we just submitted and if there are any existing sessions 00:11:37.260 --> 00:11:38.679 in the queue before ours. 00:11:39.720 --> 00:11:42.640 So we would close this screen and then wait for 00:11:42.700 --> 00:11:44.440 our adjustment to come back. 00:11:47.480 --> 00:11:50.380 Now that our preliminary adjustment is done, we would go 00:11:50.429 --> 00:11:53.059 in, take a look at the adjustment results and check 00:11:53.120 --> 00:11:54.720 to see if there are any issues. 00:11:55.120 --> 00:11:57.210 The next step would be to move on to do 00:11:57.260 --> 00:11:58.920 the horizontal free adjustment. 00:11:59.440 --> 00:12:01.040 So we'll go back to setup adjustment. 00:12:02.040 --> 00:12:04.960 You can see it automatically, it goes to the horizontal 00:12:05.010 --> 00:12:05.280 free. 00:12:06.080 --> 00:12:09.990 Now you can see that we have the results from 00:12:10.070 --> 00:12:14.760 our preliminary adjustment as well as our GVX vectors. 00:12:15.080 --> 00:12:18.420 We're going to select both of those, move them over 00:12:18.480 --> 00:12:22.340 into the included solutions, Scroll down and make sure that 00:12:22.410 --> 00:12:25.610 LOI 2, which is our hub station has been selected 00:12:25.679 --> 00:12:28.360 as three, the 3D constraint which it has. 00:12:29.080 --> 00:12:32.000 Check our project preferences, those are fine. 00:12:32.480 --> 00:12:34.520 And then select perform adjustment. 00:12:36.880 --> 00:12:42.330 And we'll close this now that our network final horizontal 00:12:42.420 --> 00:12:45.240 free adjustment has come back. 00:12:45.240 --> 00:12:48.190 You can see here, it's now added to the adjustments 00:12:48.250 --> 00:12:48.600 table. 00:12:50.040 --> 00:12:52.530 We would check in the results of that, look for 00:12:52.580 --> 00:12:56.020 certain, look for certain statistics to make sure that everything 00:12:56.070 --> 00:12:56.600 looked OK. 00:12:57.480 --> 00:12:59.400 If it does, we're going to move on to the 00:12:59.440 --> 00:13:02.200 next step, which would be to run our horizontal constrained 00:13:02.250 --> 00:13:02.760 adjustment. 00:13:03.080 --> 00:13:04.880 So let's go ahead and go back to the setup 00:13:04.920 --> 00:13:05.440 adjustments. 00:13:06.320 --> 00:13:08.800 And you can see now that the horizontal constrained adjustment 00:13:08.840 --> 00:13:09.559 has been selected. 00:13:09.559 --> 00:13:13.250 We're going to select the output from our final horizontal 00:13:13.320 --> 00:13:16.120 free adjustment as input to that adjustment. 00:13:19.760 --> 00:13:22.100 And now we're going to want to select all of 00:13:22.160 --> 00:13:24.390 the marks that we might want to hold for a 00:13:24.440 --> 00:13:27.800 horizontal constraint with the exception of our distinct CORS. 00:13:27.800 --> 00:13:30.460 So we won't select our distinct CORS, we will select 00:13:30.510 --> 00:13:30.760 none. 00:13:31.679 --> 00:13:34.450 The rest of the CORS we will hold 3D and 00:13:34.510 --> 00:13:38.490 we have the option of holding existing NGS control stations 00:13:38.559 --> 00:13:41.800 that come from our database that we've observed. 00:13:42.120 --> 00:13:45.350 Let's go ahead and leave those selected as horizontal constraints 00:13:45.400 --> 00:13:47.240 for now and click Perform Adjustment. 00:13:48.760 --> 00:13:51.700 Now, as before, we'll see the splash screen come up 00:13:51.760 --> 00:13:55.040 that tells us basically what we just submitted, and we'll 00:13:55.100 --> 00:13:56.480 go ahead and close this. 00:13:57.920 --> 00:14:01.210 So now that our horizontal constrained solutions come back, we 00:14:01.260 --> 00:14:04.230 again would check the output of the adjustments, look at 00:14:04.280 --> 00:14:07.250 the results, look at the statistics, see how our control 00:14:07.309 --> 00:14:07.520 fit. 00:14:07.640 --> 00:14:09.940 And if everything was good, we'd move on to the 00:14:09.990 --> 00:14:12.679 next step, which would be the vertical free adjustment. 00:14:12.679 --> 00:14:15.270 So we go back to the setup adjustments, and you 00:14:15.330 --> 00:14:18.309 can see that automatically it's moved down the line to 00:14:18.370 --> 00:14:19.360 the vertical free. 00:14:19.840 --> 00:14:24.200 We'll use the output from our horizontal constrained adjustment as 00:14:24.260 --> 00:14:27.040 the input to our vertical free adjustment. 00:14:28.560 --> 00:14:30.440 And now we're going to be doing something a little 00:14:30.470 --> 00:14:31.000 bit different. 00:14:31.000 --> 00:14:34.350 So now we're going to select horizontal only for our 00:14:34.420 --> 00:14:36.800 hub, just the latitude and longitude. 00:14:37.280 --> 00:14:40.110 And we're going to substitute for the vertical one of 00:14:40.160 --> 00:14:41.440 our existing benchmarks. 00:14:41.840 --> 00:14:43.120 So we know we have a few. 00:14:43.200 --> 00:14:45.740 And you can see that since we have the tie 00:14:45.800 --> 00:14:49.550 to the database to the description file that certain qualities 00:14:49.610 --> 00:14:50.880 have been shown here. 00:14:51.040 --> 00:14:53.890 So I'm going to go ahead and select breadmaker vertical 00:14:53.940 --> 00:14:56.840 only, which will be constraining its orthometric height. 00:14:57.920 --> 00:15:02.000 And again, we're constraining horizontal only on our on our 00:15:02.070 --> 00:15:05.050 hub, the CORS that was our hub and we will 00:15:05.120 --> 00:15:07.400 perform vertical free adjustment. 00:15:09.880 --> 00:15:12.770 And let's close this screen and wait for our vertical 00:15:12.820 --> 00:15:14.400 free adjustment to come back. 00:15:16.640 --> 00:15:19.720 So our vertical free adjustment has come back and again 00:15:19.780 --> 00:15:22.910 we would look through the results of that adjustment for 00:15:22.970 --> 00:15:25.880 any issues or any problems that need to be resolved. 00:15:26.760 --> 00:15:29.660 Seeing none here right now, let's go and set up 00:15:29.720 --> 00:15:32.560 for our final vertical constrained adjustment. 00:15:33.640 --> 00:15:36.580 So we'll use the network final vertical 3 as the 00:15:36.640 --> 00:15:38.720 input to our vertical constrained. 00:15:43.600 --> 00:15:47.150 And now we'll constrain any vertical that we might want 00:15:47.210 --> 00:15:49.600 to constrain in our final adjustment. 00:15:49.840 --> 00:15:53.250 And this could include stations that are considered height mod 00:15:53.300 --> 00:15:53.800 stations. 00:15:53.800 --> 00:15:57.800 These are stations that have both have been surveyed using 00:15:57.870 --> 00:16:02.700 GPS and tied into existing benchmarks using certain specifications and 00:16:02.770 --> 00:16:04.560 meeting certain standards. 00:16:05.200 --> 00:16:06.800 So these can also be constraints. 00:16:06.800 --> 00:16:09.620 Some of those could be CORS, they could be other 00:16:09.680 --> 00:16:10.200 stations. 00:16:10.200 --> 00:16:15.520 For instance, this station OU 03 has that type. 00:16:16.000 --> 00:16:23.110 So let's go ahead and and select all possible stations 00:16:23.240 --> 00:16:26.800 that have vertical control. 00:16:26.800 --> 00:16:31.620 We're going to not select station ASUB our distinct CORS, 00:16:31.700 --> 00:16:32.200 right? 00:16:32.200 --> 00:16:33.840 We don't want to constrain that one. 00:16:34.600 --> 00:16:37.870 And we have LOI 2, which we actually want to 00:16:37.950 --> 00:16:42.410 constrain in 3D latitude, launch it in orthometric height as 00:16:42.490 --> 00:16:45.760 well as the other stations of vertical only. 00:16:47.040 --> 00:16:50.320 And we want to change OU O3 to vertical only. 00:16:52.160 --> 00:16:54.560 OK, let's check our project preferences once again. 00:16:55.120 --> 00:16:58.080 And we'll select perform adjustment. 00:16:59.120 --> 00:17:01.800 And we'll close this screen and wait for our adjustment 00:17:01.850 --> 00:17:02.480 to come back. 00:17:06.040 --> 00:17:07.840 So our vertical constraint adjustment is back. 00:17:08.960 --> 00:17:12.260 We go in, review the output, review all the adjustments, 00:17:12.320 --> 00:17:15.630 review everything that we've done thus far and make sure 00:17:15.690 --> 00:17:17.280 that everything looks good. 00:17:18.240 --> 00:17:20.200 If it does, there's only a couple steps left. 00:17:21.160 --> 00:17:24.619 One of the next steps would be to upload the 00:17:24.700 --> 00:17:25.560 field logs. 00:17:26.880 --> 00:17:29.300 So I've held off on uploading those until now, just 00:17:29.340 --> 00:17:31.900 in case there was something that needed to be resolved 00:17:31.950 --> 00:17:33.040 or changed in the logs. 00:17:34.320 --> 00:17:37.560 So let's go ahead and find the link for upload 00:17:37.630 --> 00:17:38.400 field logs. 00:17:39.280 --> 00:17:39.840 There it is. 00:17:42.160 --> 00:17:43.640 So let me choose a file. 00:17:46.600 --> 00:17:48.280 Let's go to our project. 00:17:48.280 --> 00:17:52.730 Let's go to field logs, and here's our field log 00:17:52.820 --> 00:17:55.880 file open and let's upload those. 00:17:57.040 --> 00:17:59.560 Then we would go ahead and finish writing our project 00:17:59.609 --> 00:18:02.900 report, putting in all the important information about the processing 00:18:02.950 --> 00:18:04.280 and adjustments that we had. 00:18:04.359 --> 00:18:06.800 And let's click on the Upload project report. 00:18:09.800 --> 00:18:19.010 Let's choose our report and let's upload the report. 00:18:20.560 --> 00:18:24.600 And finally, after reviewing everything, getting everything uploaded, we can 00:18:24.650 --> 00:18:26.560 select the review and submit to NGS. 00:18:26.720 --> 00:18:28.119 This will give us our checklist. 00:18:28.280 --> 00:18:32.400 And if there's anything in this project that is highlighted 00:18:32.470 --> 00:18:35.960 pink or not checked, it would be something that we 00:18:36.030 --> 00:18:36.800 need to do. 00:18:36.800 --> 00:18:41.300 In this particular situation, I didn't create a project proposal 00:18:41.359 --> 00:18:42.560 for this project. 00:18:42.560 --> 00:18:45.109 So it's saying that I don't have a project proposal 00:18:45.160 --> 00:18:48.270 tracking number, which was should be listed in the preferences 00:18:48.320 --> 00:18:48.720 section. 00:18:48.720 --> 00:18:49.920 And we knew that that existed. 00:18:50.440 --> 00:18:52.970 So if that was there, I could go ahead and 00:18:53.030 --> 00:18:56.390 click the Submit for publication button up here and that 00:18:56.450 --> 00:18:58.800 would be the end of the project for us. 00:19:01.480 --> 00:19:04.480 This module was written and narrated by Dan Martin and 00:19:04.540 --> 00:19:06.040 recorded in September 2024. 00:19:06.840 --> 00:19:09.960 For more information, please visit the OPUS Projects homepage.