V.Diff

[Jim Frame]

I've always interpreted the V.Diff display as an indicator of how the vertical component of the solution is moving, but I don't know what's actually being measured. Both figures appear to be denominated in millimeters. What quantities do they represent?

PS With most equipment a question like this would send me to the manual, but as another poster noted recently, the LS manual is so badly out of date that I no longer look to it as a useful reference.

 

[Javad]

Hi Jim, You are correct that our user manual is outdated. We will correct that. Meanwhile please look at the "Help" hardware button and see "Linear Vertical Drift" for the definition of V.Drift. We update the Help button more often that the user manual. Your point well taken.

 

[Jim Frame]

The definition of V.Drift (I mistakenly wrote V.Diff above) in the Help section doesn't answer my question. The display indicates millimeters, but millimeters per what? Per epoch, per second, accumulated average, something else? And does the figure in parentheses indicate the RMS of the net vertical drift?

Answers to these questions won't impact my procedures, but I like to understand what I'm looking at while collecting data. And there's a lot to look at that I still don't understand!

Thanks!

 

[Shawn Billings]

RMS is for the slope as I recall. A slope that is close to zero is desired. Slope above zero indicates possible influence by multi path.

 

[Javad]

It is "Linear Vertical Drift". Vertical scale is mm and horizontal is epoch/time. A straight line is fitted to the date and the slope of that line is the drift. The RMS is the deviations from the straight line. A high drift means that the solution was drifting. If there is oscillation on the vertical graph and the result of the fitted line does not have a big drift, it is an indication that solution is stable. Experience in your work area lets you compare the situations.

 

[Jim Frame]

Thanks for the clarification!

 

[Javad]

I still owe you to update our user manual. Do not let me off the hook easy!

 

[Nate The Surveyor]

Mr javad, we don't let you off hook easy!

Nate

 

[Steve Douty]

I still owe you to update our user manual. Do not let me off the hook easy!

We all know that you are always updating the system and therefore the screens and functions are always changing. We all love the updates and increased functionality and hate that the manuals can't keep up. And being surveyors, resist any change. Although the manual is one of the best in the industry I can see that it will be hard to keep it current.

I would like to make two suggestions:
1) Change the page numbering system. The present manual is numbered consecutively; this means that if you make edits that increase or decrease the number of pages the table of contents and index must all be changed and the entire manual must be republished. I would suggest you consider a system of sections relating to task. If a system like this is put in place you can add pages and even entire sections without without changing the whole manual.
2) Consider placing the manual online with sections that can be added to or changed by the users (once reviewed by you). This might be similar to Wikipedia. I am certain that many users have thoughts that the would be happy to share and many of us would like to hear their thoughts.

 

[Javad]

How about if we make the manual in several small volumes bonded separately? For example
Volume 1: Generals, pages, tags, points, etc.
Volume 2: RTK, verifications, Base-Rover setup.
Volume 3: Stakeout and Alignment
Volume 4: J-Mate
Volume 5: ....
If you agree, make your suggestions on volume divisions.

 

[Javad]

Mr javad, we don't let you off hook easy!

Nate

OK, The dangerous surveyor! I will watch out for you!

 

[Steve Douty]

How about if we make the manual in several small volumes bonded separately? For example
Volume 1: Generals, pages, tags, points, etc.
Volume 2: RTK, verifications, Base-Rover setup.
Volume 3: Stakeout and Alignment
Volume 4: J-Mate
Volume 5: ....
If you agree, make your suggestions on volume divisions.

I think the idea of publishing in volumes will work nicely. I would suggest you consider a volume for each button on the home screens. Collect, Stake, Coord System, etc. Each volume could then have a chapter that relates to the sub menus, and each sub chapter could have sub sections:

CoGo
Chapter 1; Basic
Chapter 2; Offset
Section a; Offset
Section b; To Line 1
.
.
.

This would have the advantage of isolating the page numbering to be unique to individual chapters and sub sections, adding or deleting chapters, and be self-indexing. It would also allow the user to know where the commands are located.

Although the bound volumes are impressive, I feel that a manual that could be updated by adding and deleting chapters or pages would be more useful to the end user. We all know that you and your team will revise something before the ink is dry. This is a good thing. Specialized ring binders of different sizes, number of rings, quality of cover, and quality and versatility of the rings can be purchased.

I am looking for a manual that can grow with the product, can be edited by the JAVAD team, added to by the user and be cost effective. It would also be nice if you would pay us to use them!

Thanks for encouraging us to share.

 

[Javad]

Some of our PLS folks are against several volumes. They want all in one book.
Also the age of printed documents is over. We will should get used to the on-line manuals that have hyper text too. We can update that weekly (which we have not done so far!).
Probably we kill one tree for each user manual.

 

[Steve Douty]

Some of our PLS folks are against several volumes. They want all in one book.
Also the age of printed documents is over. We will should get used to the on-line manuals that have hyper text too. We can update that weekly (which we have not done so far!).
Probably we kill one tree for each user manual.

I agree that there is no need for a printed manual. Whatever you call the organization of the new manual will work great. (Volumes, chapters, sections or any other method of numbering pages so the user can use it without constantly changing the page numbers in the whole manual every time there is an update will make our life better.) I like the use of hyper text.