Realworks processing hardware

Discuss Trimble hardware here.
Post Reply
Lennart
I have made <0 posts
I have made <0 posts
Posts: 1
Joined: Wed Jun 21, 2017 12:44 pm
6
Full Name: Lennart Querelle
Company Details: GeoNext
Company Position Title: Specialist
Country: Netherlands

Realworks processing hardware

Post by Lennart »

At the office, we use Trimble Realworks to register our scans from the TX8. We use spheres of 121 mm and they are measured with GPS and a Total Station, because we need an accuracy of below 10 mm. At this time, the processing takes a lot of time. Automatic registration does often not work very well, so we must do it manually.

Realworks is not running very well on our systems, switching between stations takes about 3-5 seconds, selecting a sphere around 4 seconds, etc. At busy day’s we must register around 100 scans/day and if you count the time I must wait it is 1-2 hours a day, which in my opinion is a lot of time and lost productivity.

Of course, our systems meet the requirements of Trimble itself, but those requirements are not that high. They do say in their manual “Trimble highly recommends that users acquire the most powerful hardware configuration available at the time of purchase”, but that’s a little vague in my opinion, that can be everything.

I’ve tried Realworks here with different systems, but they all have the same issues.
Systems in use:
i7-4770K - 32 GB RAM – GTX 960
i7-6700 – 32 GB RAM – GTX 960
i7-6700HQ – 16 GB RAM – Quadro M600M
All with normal SATA SSD’s (where all the projects are stored on)

What are your experiences and does Realworks works a lot faster on better systems? For example, a workstation with a professional Xeon or i7-6950X CPU, GTX1080/RX580 or Firepro/Quadro graphics card, faster SSD (PCI-e) or a RAM disk.
Or is the code just badly written and can’t it work any faster, no matter what system you use?
And of course, we’re running the latest version, 10.3
User avatar
vincent denis
V.I.P Member
V.I.P Member
Posts: 166
Joined: Fri Nov 16, 2012 9:25 am
11
Full Name: Vincent Denis
Company Details: GEOMESURE
Company Position Title: Technical Sales Engineer
Country: France
Linkedin Profile: Yes
Been thanked: 3 times
Contact:

Re: Realworks processing hardware

Post by vincent denis »

I'm agry with your post.

Manual registration with RealWorks is not user friendly. I use it on a Xeon - 32gb ram - Quadro K4000 and when i swith 2 stations it freeze during 3-5 second.
I think it's the system use this time to load point cloud on cache system. On the contrary of Cyclone who use database to be more faster ....

If Realworks developper can hear us, and fix it. Realworks may becaume the best register software ......
jaredmatthews
V.I.P Member
V.I.P Member
Posts: 202
Joined: Sun Sep 13, 2015 7:19 pm
8
Full Name: Jared
Company Details: Sova Surveys Limited
Company Position Title: Director
Country: UK
Skype Name: jaredmatthews
Linkedin Profile: Yes
Has thanked: 5 times
Been thanked: 13 times
Contact:

Re: Realworks processing hardware

Post by jaredmatthews »

Hi Lennart.

I currently run realworks 10.3 on a laptop with the following system:

Intel i7-6820HK CPU @2.70GHz - 32G RAM - GTX 980M

I also have a normal SSD (not solid state).

With all this, I am able to run realworks relatively fast. I do not have the waiting time of about 3-5 seconds. I do not use spheres, so I can not comment on the sphere selection.

So with that said, I am sure that your hardware requirements should be up to the task.
I have come across some issues with Realworks in the past, and found that a .NET update (google it) sometimes fixes issues.

If not, get trimble support on the case
User avatar
vincent denis
V.I.P Member
V.I.P Member
Posts: 166
Joined: Fri Nov 16, 2012 9:25 am
11
Full Name: Vincent Denis
Company Details: GEOMESURE
Company Position Title: Technical Sales Engineer
Country: France
Linkedin Profile: Yes
Been thanked: 3 times
Contact:

Re: Realworks processing hardware

Post by vincent denis »

jaredmatthews wrote: Thu Jun 22, 2017 1:50 pm Hi Lennart.

I currently run realworks 10.3 on a laptop with the following system:

Intel i7-6820HK CPU @2.70GHz - 32G RAM - GTX 980M

I also have a normal SSD (not solid state).

With all this, I am able to run realworks relatively fast. I do not have the waiting time of about 3-5 seconds. I do not use spheres, so I can not comment on the sphere selection.

So with that said, I am sure that your hardware requirements should be up to the task.
I have come across some issues with Realworks in the past, and found that a .NET update (google it) sometimes fixes issues.

If not, get trimble support on the case
I Jarred,

When you use Realworks cloud to cloud process. to select stations, or switch them, you don''t have to wait? It's instant? no freeze ?
jaredmatthews
V.I.P Member
V.I.P Member
Posts: 202
Joined: Sun Sep 13, 2015 7:19 pm
8
Full Name: Jared
Company Details: Sova Surveys Limited
Company Position Title: Director
Country: UK
Skype Name: jaredmatthews
Linkedin Profile: Yes
Has thanked: 5 times
Been thanked: 13 times
Contact:

Re: Realworks processing hardware

Post by jaredmatthews »

Vincent.

If I understand you correctly, you mean when you have the Reference cloud (usually RED) and are adding the moving cloud (usually GREEN)...

There may be a slight delay as the new moving cloud is loaded, but no freezing or anything.

If you could post a video of how it freezes so I can see, maybe that would help explain
ArnaudO
I have made <0 posts
I have made <0 posts
Posts: 1
Joined: Wed Jun 07, 2017 8:24 am
6
Full Name: Arnaud OLLIVIER
Company Details: Geotopo
Company Position Title: Pre sale engeener
Country: France
Linkedin Profile: No

Re: Realworks processing hardware

Post by ArnaudO »

Hi,

First, it's strange if the automatic registration does often not work. Maybe your sphere is to far from the scanner for their size.

After, there are differents parameters which cause these little freezing.
An SSD hard drive is best to work faster.

TRW loads pointcloud in the cache. Until 150 or 200 scans following your configuration, you should not have freezing for manually registration with targets. (Maybe a little, with point cloud registration.)

Normally, manually registration is just to correct some failed scan registration and not to work on all the project. If the automatic registration doesn't works very well, you need to make adjustement on the field.

So theses freezing on a large project may arrive for some data.
If you wants to works manually on a big project, you need to create differents project (per 150 scans) which you will merge after to make a final compensation.

Arnaud O
Post Reply

Return to “Trimble”