Hi Patrick et al,
on the same set of grids. That is, the idea is to use these functions
> first, before any size interpolation. This is at least indicated in the
> documentation of assp_interp_size.m.
>
>
> No time for me to dig into the Python code (and anyhow don't have the
> latest version
Hi Patrick,
I am not actually directly calling any assp functions. I use rttov.get_assp as
shown below to get what I need and send the new grids for f, T, and dveq along
with the habit ID (I have been playing with allow_extrap to just allow to fill
the gap for now but I know it may not be a
Hi,
Some quick input, for clarification.
At least for the Matlab interface there are functions for interpolating
in frequency, angular grid and temperature, to get the data of all sizes
on the same set of grids. That is, the idea is to use these functions
first, before any size
HI Vasileios,
Thanks for the hints. Meanwhile, I spent sometime and wrote a piece of code to
read the data in and interpolate them. I will they to see if can fix it
according to what you suggested. In any case, once you have fixed the code, I
will compare what I have developed with the main
Hello Isaac,
I had a brief look at assp_interp_size. Indeed there are some bugs in this
function that need to be fixed. I will allocate some time on this next week;
sorry for any inconvenience caused. For the time being, I could give you some
hints:
To use this function, all elements in S
Hi Patrick,
Thanks for your quick answer.
Simon's answer did clarify it and I believe his solution is quite close to what
you suggest and what is done in Qpack.
I'll try it out.
Thanks,
Eric
De : Simon Pfreundschuh
Envoyé : vendredi 4 juin 2021 14:55:24
Sorry, though the response would automatically go to the list. For completeness,
here's my response from earlier.
Just to clarify and confirm:
> same sensors, same atmosphere, etc.. just different measurements vectors using
> OEM from ARTS directly ?
This is what ARTS currently does: It takes
Eric,
I am performing strato-mesospheric ozone retrievals with the OEM
implemented directly in ARTS (using the python interface).
As my sensor is not changing much with time, I am wondering if there is
a way (and if this is worth in terms of computation speed) to reuse the
sensor_response
Dear ARTS community,
I am performing strato-mesospheric ozone retrievals with the OEM implemented
directly in ARTS (using the python interface).
As my sensor is not changing much with time, I am wondering if there is a way
(and if this is worth in terms of computation speed) to reuse the
