The Off Topic Thread.

[Never had any say Panda]

Good.... Yes...

Yourself?

[.Stripes.]

I'm alright...just watching some tv. Spent today playing with trigonometry...I dislike trigonometry...

How's mini panda going? Recovering?

[Never had any say Panda]

Yeah he's doing well.. I had a few hours break from caring duties and went out for dinner with a friend tonight.. That was nice..

Why do you hate trigonometry?

It's really quite easy provided you remember your little rhymes..

Some Old Hags Can't Always Hide Their Old Age..

[.Stripes.]

That's good, glad to hear he's on the mend and you're getting some of your own recovery time.

SOHCAHTOA is easy, it's this kind of stuff I was playing with:

http://www.drillingformulas.com/radius-of-curvature-method/

That was ok by itself, but when comparing the calculations I setup in excel brought to light that they don't match what gets plotted by our 3D software package...despite it saying it uses a certain Desurvey method (which I then calculated each point in excel using that method, correctly too coz I double checked)...so I'm going to email the company in the morning to ask how the program actually calculates the xyz data.

[Pixy Angel]

At work trying hard to stay awake.

[Never had any say Panda]

Morning all..

Yeah stripes that ain't fun.. The biggest one for me would be knowing how the data gets into the 3D software.. If it's fed in straight from the survey equipment there ain't much that can go wrong..

If it's post processed there is a huge margin for operator error..

What 3D software are you using?

[Never had any say Panda]

Bit late to edit..

Nothing to do with excel working in radians from memory stripes?

[Corzza]

Sooooo...how's everybody doin?

Freezing my bolacks off!

[.Stripes.]

I'll email Maptek today, we're using Vulcan.

Essentially the data we have from drilling is like the example in the link I posted but with surveys taken every 20m over the length of the hole. Oh and I've converted to radians in the spreadsheet (used the radians function).

I woke up with a thought this morning though (my life is sad). The data gets spit out into a CSV file, so it gets truncated to how ever many decimal places are visible in the original spreadsheet when the CSV saves. So in this case it's truncating to 1 decimal place, which is what Vulcan then sees and calculates from. So I'll play with that this morning and see what difference that makes.

Edited 11/08/14 09:35 PM by .Stripes.

[Never had any say Panda]

Ah yeah.. Multiple civil program's work upwards of 8-15 decimals. Does tend to give different results when the roundings change..