Dear ARTS community,
In order to try a recent fix suggested and implemented (commit n.
5951a72fbef6d7ac9a3de8d2c503b58ef5af7d17, fromTyphon mailing list) on the
development version of ARTS I came into another problem trying to implement my
ground-based retrievals through PyARTS. In fact, I can
Hi,
There is the same/similar problem on the Matlab side (as there is no
writing and reading of xml-files including the time group).
So a general hint for all. If you just want to set sensor_time to some
value, you can do this by these method calls
timeNow
ArrayOfTimeSetConstant( sensor_tim
Dear Patrick,
Thanks a lot for the quick answer.
It seems indeed to define the sensor_time correctly in an ARTS file using your
2 lines.
On the PyARTS side, it seems that the defintion of ws.sensor_time is fine as
well but I can't access its value ("ws.sensor_time.value" fails, but not sure
Hi,
This is my fault. Explanation if wanted: sensor_time is now a different
type. It now stores actual time stamps like "1970-01-01 01:00:01" (which
is what "1" means in time stamps if you are in CET).
I will fix it so you can set the time from a numpy array again in pyarts.
However, I don't u
Dear Richard,
Thanks for the detailed explanation.
I used the following line as a workaround for now and it seems to work fine.
ws.timeNow()
ws.ArrayOfTimeSetConstant(ws.sensor_time, 1, ws.time)
No stress then but I am looking forward to your new implementation.
Thanks again and best regar
