Re: [arts-users] pyARTS OEM Error?

2023-06-30 Thread Mathias Milz
Hi Oliver,

I did some tries but maybe not sufficient. I’ll try your suggested extension.

Cheers,
Mathias

On 2023-06-30, 13:56, "Lemke, Oliver"  wrote:
Hi Mathias,

A couple of ideas:

1. Since the frequency value in the error output has only 5 digits after the 
decimal[1], it might well be that your extension by 700 kHz is not sufficient 
and still leads to the same error message due to rounding. I'd propose to 
extend f_grid by 2 MHz and see if that fixes the problem.

2. You probably did this but to be sure I'll ask anyway: Did you recalculate 
the lookup table after extending the f_grid?

Cheers,
Oliver

[1] we'll apply a fix to improve that output


> On 30. Jun 2023, at 09:00, Mathias Milz 
> mailto:mathias.m...@ltu.se>> wrote:
>
> Dear all,
>  Maybe someone here can help me:
>
> I set up a new retrieval for high resolving spectrometer using pyARTS with 
> OEM. Since it covers a wider range of the spectrum with higher resolution, 
> I've expanded the f_grid accordingly (with relatively high resolution, lower 
> than the spectrum).
>  pyARTS calculates the LookUp Table as it should.
>  If the run then goes into ws.OEM, then it stops  with the error message 
> below.
> I extended the spectrum by 700kHz and the error occurs again.
>  According to the error message, it happens in yCalc.
>  What makes me suspisious: The pure forward calculation withy Calc (i.e. 
> without OEM call) with the LUT read in runs perfectly.
>  Does anyone here have an idea what the problem could be?
>  Thanks in advance
>  Mathias
>   And here the error message:
> Run-time error in method: yCalc
> User Error: failed
> Error is found at:
> 
> /usr/local/miniconda/envs/pyarts-build/conda-bld/pyarts_1675241025317/work/src/m_rte.cc:2774
> Please follow these instructions to correct your error:
> User Error: failed
> Error is found at:
> 
> /usr/local/miniconda/envs/pyarts-build/conda-bld/pyarts_1675241025317/work/src/rte.cc:1750
> Please follow these instructions to correct your error:
> Run-time error in function: iyb_calc
> Run-time error in agenda: iy_main_agenda
> Run-time error in method: iyClearsky
> User Error: do_abort
> Error is found at:
> 
> /usr/local/miniconda/envs/pyarts-build/conda-bld/pyarts_1675241025317/work/src/m_rte.cc:656
> Please follow these instructions to correct your error:
> Error messages from failed cases:
> Runtime-error in source calculation at index 122:
> Run-time error in agenda: propmat_clearsky_agenda
> Run-time error in method: propmat_clearskyAddFromLookup
> Problem with gas absorption lookup table.
> At least one frequency is outside the range covered by the lookup table.
> Your new frequency value is 2.32501e+11 Hz.
> The allowed range is 2.295e+11 to 2.32501e+11 Hz. Runtime-error in source 
> calculation at index 162:
> Run-time error in agenda: propmat_clearsky_agenda
> Run-time error in method: propmat_clearskyAddFromLookup
> Problem with gas absorption lookup table.







Re: [arts-users] pyARTS OEM Error?

2023-06-30 Thread Lemke, Oliver
Hi Mathias,

A couple of ideas:

1. Since the frequency value in the error output has only 5 digits after the 
decimal[1], it might well be that your extension by 700 kHz is not sufficient 
and still leads to the same error message due to rounding. I'd propose to 
extend f_grid by 2 MHz and see if that fixes the problem.

2. You probably did this but to be sure I'll ask anyway: Did you recalculate 
the lookup table after extending the f_grid?

Cheers,
Oliver

[1] we'll apply a fix to improve that output


> On 30. Jun 2023, at 09:00, Mathias Milz  wrote:
> 
> Dear all,
>  Maybe someone here can help me:
> 
> I set up a new retrieval for high resolving spectrometer using pyARTS with 
> OEM. Since it covers a wider range of the spectrum with higher resolution, 
> I've expanded the f_grid accordingly (with relatively high resolution, lower 
> than the spectrum).
>  pyARTS calculates the LookUp Table as it should.
>  If the run then goes into ws.OEM, then it stops  with the error message 
> below.
> I extended the spectrum by 700kHz and the error occurs again.
>  According to the error message, it happens in yCalc.
>  What makes me suspisious: The pure forward calculation withy Calc (i.e. 
> without OEM call) with the LUT read in runs perfectly.
>  Does anyone here have an idea what the problem could be?
>  Thanks in advance
>  Mathias
>   And here the error message:
> Run-time error in method: yCalc
> User Error: failed
> Error is found at:
> 
> /usr/local/miniconda/envs/pyarts-build/conda-bld/pyarts_1675241025317/work/src/m_rte.cc:2774
> Please follow these instructions to correct your error:
> User Error: failed
> Error is found at:
> 
> /usr/local/miniconda/envs/pyarts-build/conda-bld/pyarts_1675241025317/work/src/rte.cc:1750
> Please follow these instructions to correct your error:
> Run-time error in function: iyb_calc
> Run-time error in agenda: iy_main_agenda
> Run-time error in method: iyClearsky
> User Error: do_abort
> Error is found at:
> 
> /usr/local/miniconda/envs/pyarts-build/conda-bld/pyarts_1675241025317/work/src/m_rte.cc:656
> Please follow these instructions to correct your error:
> Error messages from failed cases:
> Runtime-error in source calculation at index 122: 
> Run-time error in agenda: propmat_clearsky_agenda
> Run-time error in method: propmat_clearskyAddFromLookup
> Problem with gas absorption lookup table.
> At least one frequency is outside the range covered by the lookup table.
> Your new frequency value is 2.32501e+11 Hz.
> The allowed range is 2.295e+11 to 2.32501e+11 Hz. Runtime-error in source 
> calculation at index 162: 
> Run-time error in agenda: propmat_clearsky_agenda
> Run-time error in method: propmat_clearskyAddFromLookup
> Problem with gas absorption lookup table.






smime.p7s
Description: S/MIME cryptographic signature


[arts-users] pyARTS OEM Error?

2023-06-30 Thread Mathias Milz
Dear all,

Maybe someone here can help me:

I set up a new retrieval for high resolving spectrometer using pyARTS with OEM. 
Since it covers a wider range of the spectrum with higher resolution, I've 
expanded the f_grid accordingly (with relatively high resolution, lower than 
the spectrum).

pyARTS calculates the LookUp Table as it should.

If the run then goes into ws.OEM, then it stops  with the error message below.
I extended the spectrum by 700kHz and the error occurs again.

According to the error message, it happens in yCalc.

What makes me suspisious:
The pure forward calculation withy Calc (i.e. without OEM call) with the LUT 
read in runs perfectly.

Does anyone here have an idea what the problem could be?

Thanks in advance

Mathias


And here the error message:
Run-time error in method: yCalc
User Error: failed
Error is found at:

/usr/local/miniconda/envs/pyarts-build/conda-bld/pyarts_1675241025317/work/src/m_rte.cc:2774
Please follow these instructions to correct your error:
User Error: failed
Error is found at:

/usr/local/miniconda/envs/pyarts-build/conda-bld/pyarts_1675241025317/work/src/rte.cc:1750
Please follow these instructions to correct your error:
Run-time error in function: iyb_calc
Run-time error in agenda: iy_main_agenda
Run-time error in method: iyClearsky
User Error: do_abort
Error is found at:

/usr/local/miniconda/envs/pyarts-build/conda-bld/pyarts_1675241025317/work/src/m_rte.cc:656
Please follow these instructions to correct your error:
Error messages from failed cases:
Runtime-error in source calculation at index 122:
Run-time error in agenda: propmat_clearsky_agenda
Run-time error in method: propmat_clearskyAddFromLookup
Problem with gas absorption lookup table.
At least one frequency is outside the range covered by the lookup table.
Your new frequency value is 2.32501e+11 Hz.
The allowed range is 2.295e+11 to 2.32501e+11 Hz. Runtime-error in source 
calculation at index 162:
Run-time error in agenda: propmat_clearsky_agenda
Run-time error in method: propmat_clearskyAddFromLookup
Problem with gas absorption lookup table.