Maybe we can trade links if you would like. I have no problem at all with that. Let me know and I will talk to the others in our group. I know you are in the UK right? I am in Houston, Texas USA.
I'm interested in how the interface works...What kind of files does it require?
Does it rebuild data in PDMS or just sort of "referrence" the data? How is the speed?
Are you coming to the Viewpoint Americas/ISEIT Conference in Oct. One of the topics for discussion and presentation will go over Laser Scanning. Come check it out. You can get agenda and registration information from our site.
[QUOTE=wheels]I'm interested in how the interface works...What kind of files does it require?
Does it rebuild data in PDMS or just sort of "referrence" the data? How is the speed?
I was involved in writing the prototype of the interface - some details may have changed since I worked on it, but I think the basics are unchanged.
It "sort of references" the detailed data - using software libraries supplied by the Laser data supliers. The low-level display code in PDMS calls out to the Laser system to get details of the points in the area of interest, and displays them integrated with the PDMS Model. PDMS does store a sort of "skeleton" of the Laser-data though, to help with clashing and knowing where the data is.
The speed seemed OK when I tried it, but it really helped to have the Laser data on your local machine rather than accessed across the network. (Note, I only worked with data from one of the Laser systems, and significant work happened on the project after I moved to other things so the performance characteristics may have changed since)
[QUOTE=TimSharrock]I was involved in writing the prototype of the interface - some details may have changed since I worked on it, but I think the basics are unchanged.
It "sort of references" the detailed data - using software libraries supplied by the Laser data supliers. The low-level display code in PDMS calls out to the Laser system to get details of the points in the area of interest, and displays them integrated with the PDMS Model. PDMS does store a sort of "skeleton" of the Laser-data though, to help with clashing and knowing where the data is.
The speed seemed OK when I tried it, but it really helped to have the Laser data on your local machine rather than accessed across the network. (Note, I only worked with data from one of the Laser systems, and significant work happened on the project after I moved to other things so the performance characteristics may have changed since)
Tim
Welcome to the forum Tim! I see the words has gone out...
I always appreciated YOUR views on the Aveva products on the old forum.
How is the Stress C coming? Are you involved in that?
I have seen some write up about bi-directional linking between CII -> PDMS 11.6.
If your looking for stress interfaces and the stress-c is not complete or functional. We tested out CAEPIPE from www.sstusa.com. They have a fully functional stress package and interface with PDMS that works great. I have spoke with the owner and main developer to help with PDMS testing. Send me a PM for more information.
[QUOTE=de_ding]
How is the Stress C coming? Are you involved in that?
I have seen some write up about bi-directional linking between CII -> PDMS 11.6.
I am involved in too many things! Yes PSI (the successor to STRESS-C) is very nearly ready for general release - a few issues have come up from the new-product acceptance procedure, but I hope they won't take long to resolve.
Yes it is indeed 2-way - you can import deflected shapes back from CAESAR II, and also changes in the piping layout. What you get back is a sort of "dummy pipe" - we decided that we could not modify the original pipe safely, but you get an equivalent that you can clash-check with, and use as construction geometry when applying any changes for real.
