TELEMAC-MASCARET Forum: ORIGIN COORDINATES disabled in v7p1r0? (1/1)

Welcome, Guest

TOPIC: ORIGIN COORDINATES disabled in v7p1r0?

ORIGIN COORDINATES disabled in v7p1r0? 8 years 9 months ago #19648

pilou1253 OFFLINE openTELEMAC Guru Posts: 584 Thank you received: 106	Hi! I have just installed v7p1r0 and noticed that my result files are not translated back into my original coordinate system if I include the ORIGIN COORDINATES keyword (I vizualize results with Blue Kenue). It has been working fine with v7p0r1. Has something been done in v7p1r0? Best regards PL
	The administrator has disabled public write access.

ORIGIN COORDINATES disabled in v7p1r0? 8 years 9 months ago #19651

jmhervouet

Hello,

Hum, this was a discussion among developers and it was decided that it was no longer useful to have this shift as soon as we can have the double precision format, so this should be advertised and put in the documentation, or module Hermes should be corrected. I was keen to keep the possibility of a shift as such for compatibility, so in view of your message it's going to be another discussion here...

With best regards,

Jean-Michel Hervouet

The administrator has disabled public write access.

ORIGIN COORDINATES disabled in v7p1r0? 8 years 9 months ago #19653

yugi OFFLINE openTELEMAC Guru Posts: 851 Thank you received: 244	Hi, You have a couple solution if you what to change the coordiantes : - Using Corrxy - using converter.py with the option --dx= and --dy= that translate the file for the given values. Hope it helps
	There are 10 types of people in the world: those who understand binary, and those who don't. The administrator has disabled public write access.

ORIGIN COORDINATES disabled in v7p1r0? 8 years 9 months ago #19654

pilou1253
OFFLINE
openTELEMAC Guru
Posts: 584
Thank you received: 106

Hi,

Thanks for your answers.

I am mainly thinking of compatibility reasons with older versions, when there are existing Blue Kenue workspaces etc...
If it doesn't cost anything to let the option available, why removing it?

I know that we can use corrxy or converter.py for that purpose, but it then become a new workflow. It certainly isn't a big issue for regular users but can be an extra source of confusion for those who only run a few models per version in the best case.

Is there a chance that Blue Kenue will release a new version able to deal with double precision coordinates?

Best regards
PL

The administrator has disabled public write access.

ORIGIN COORDINATES disabled in v7p1r0? 7 years 2 months ago #27780

yohannis OFFLINE Fresh Boarder Posts: 22 Thank you received: 9	Hello! How did the discussion regarding coordinate shift end? Is there any plan to go back to the older way in the next releases? We would also like to have the compatibility with previous versions for similar reasons as pilou1253. Best regards, Yohannis
	The administrator has disabled public write access.