I have borrowed two R10s, that gives me 4 receivers. I am planning on running an OPUS Projects session tomorrow and it has been a while since I did one. I will be leaving one stationary and moving the other three around. At one time there was talk about using shorter sessions and OPUS RS but I can't find anything saying NGS ever implemented that. Assuming everything must go thru OPUS S, that is 2 hours minimum.
Now my question, Do I need to have the same 2 hours on the three receivers that will be moved or can they be staggered?
In other words, Do I move all three and when I get the last one started logging, THEN start timing 2 hours and a few minutes?
I can't find my notes and it has been almost three years. I expect this to take about 12 hours.
Thanks,?ÿ James
OPUS Projects only works with OPUS Static for now, with a minimum of 2 h0ur sessions.?ÿ If you are moving the rovers around, the sessions should be set automatically, but if your start time?ÿ of the last receiver is too late, you may have to adjust the sessioning parameter. ?ÿ?ÿ I suggest that you get at least 1.5 hours of common data.?ÿ Are you going to process to the CORS or do a local network??ÿ OPUS Projects would be happiest if you for example started all your observations at 0800 and ended them at 1015, then started the next session at 1045 and ended at 1300.?ÿ Do you have the ability to program start times in the R 10??ÿ
Thanks Steve,
I managed to muddle my way thru it without any serious issues. Started at 8pm Friday and finished at 2pm Saturday. I had my base receiver on my primary control point 1 for the whole 18 hours and moved the other three around. I made sure all the sessions except the base stopped before a spike at 3am and then started again. I had one opus return showing 0.226m vertical error and one showing 0.137m vertical error. It was getting close to noon and another spike. At that point, it is what it is and it is 170 miles from home.
I processed it using the nearest cors as the hub. The one showing 0.226m vertical error still had 0.068m error after the final adjustment. I had shot it and another close by with a level before starting.?ÿ I logged both points overlapping at close to the same time, both with R10s,?ÿ but only one had excessive error.
I started a different project with the base as my only point for 18 hours and processed it to the 7 cors. Using that lat long and height in the first project, I constrained the base point 1 as my hub and processed it again. The error in the bad point came out of it and I got within 0.02 feet of what I shot with a level between it and the nearby point.
Looking back, I would do a few things differently but I proved what I set out to prove and I learned along the way. First thing learned, don't drive 170 miles, work 18 hours, and then drive back!
James
Unless it's very widely spaced control, 2hrs is excessive, the rule was always 10 minutes plus one minute per mile, of course 10 minutes always turned into longer occupations. Plus with a minimum of 2 hrs per point that's at least 4 hrs on every point to do a static network.?ÿ
The 2 hours requirement in OPUS Projects (OP) is a logistical requirement at this point.?ÿ Since OP currently only ingests data uploaded to OPUS-Static, all sessions have to be 2+ hours.?ÿ Stay tuned to your NGS Newsletter of choice for updates on enhancements to OPUS and OP, we're working on it.
