search

baltrad / bropo

Anomaly (non-precipitation echo) detection and removal
Other
0 stars 0 forks source link

Traceback in ropo_realtime when quantity is missing #2

Open andershenja opened 3 years ago

andershenja commented 3 years ago

Jul 21 12:29:30 co-0181 PGF[rave.baltrad.eu]: ERROR Failure during processing#012Traceback (most recent call last):#012 File "/opt/baltrad/bropo/share/bropo/pyropo/ropo_quality_plugin.py", line 53, in process#012 obj = ropo_realtime.generate(obj, reprocess_quality_flag, quality_control_mode)#012 File "/opt/baltrad/bropo/share/bropo/pyropo/ropo_realtime.py", line 237, in generate#012 ret = process_pvol(inobj, options, quality_control_mode)#012 File "/opt/baltrad/bropo/share/bropo/pyropo/ropo_realtime.py", line 208, in process_pvol#012 scan = process_scan(scan, options, quality_control_mode)#012 File "/opt/baltrad/bropo/share/bropo/pyropo/ropo_realtime.py", line 146, in process_scan#012 newscan, gates = PadNrays?(scan, options)#012 File "/opt/baltrad/bropo/share/bropo/pyropo/ropo_realtime.py", line 267, in PadNrays?#012 dbzh = scan.getParameter("DBZH").clone()#012AttributeError: 'NoneType?' object has no attribute 'clone'

MilkaRadojevic commented 7 months ago

Hi @andershenja, At Météo France, our IT service shared with us the same type of error written in /var/log/messages. This error message is not visible in execution logs of odc_toolbox.

 Apr  2 15:52:17 sotrtm28-sine PGF[rave.baltrad.eu]: ERROR    Failure during processing#012Traceback (most recent call last):#012  File "/SOPRANO/dso/cirrus_modules/toolbox3/share/bropo/pyropo/ropo_quality_plugin.py", line 52, in process#012    import ropo_realtime#012  File "/SOPRANO/dso/cirrus_modules/toolbox3/share/bropo/pyropo/ropo_realtime.py", line 29, in <module>#012    import _fmiimage#012SystemError: offset() method: bad call flags

Can you please solve this issue. Thanks!

andershenja commented 7 months ago

I think it already should be solved in newer versions of bropo... It's due to a change that came in python3.8. It should have been solved from bropo-build-24.

Brgs Anders

Den ons 10 apr. 2024 kl 11:56 skrev Milka-Radojevic-MF < @.***>:

Hi @andershenja https://github.com/andershenja, At Météo France, our IT service shared with us the same type of error written in /var/log/messages. This error message is not visible in execution logs of odc_toolbox.

Apr 2 15:52:17 sotrtm28-sine PGF[rave.baltrad.eu]: ERROR Failure during processing#012Traceback (most recent call last):#012 File "/SOPRANO/dso/cirrus_modules/toolbox3/share/bropo/pyropo/ropo_quality_plugin.py", line 52, in process#012 import ropo_realtime#012 File "/SOPRANO/dso/cirrus_modules/toolbox3/share/bropo/pyropo/ropo_realtime.py", line 29, in #012 import _fmiimage#012SystemError: offset() method: bad call flags

Can you please solve this issue. Thanks!

— Reply to this email directly, view it on GitHub https://github.com/baltrad/bropo/issues/2#issuecomment-2047080997, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHWXQY2IJTDYS2FIEEJ7RHLY4UEEBAVCNFSM5EEK5V2KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBUG4YDQMBZHE3Q . You are receiving this because you were mentioned.Message ID: @.***>

MilkaRadojevic commented 7 months ago

Excellent. The corrected version were tested, right?

I forgot to mention that the error messages is related to the bropo-build-21, the version available at the time of building Cirrus composite production on Rocky Linux.

Should I clone the latest bropo?

andershenja commented 7 months ago

Yes, it has been tested using the automatic tests. It should automatically be done when running tests on a python version >= 3.8 since all test cases will fail.

I just fetched the code, checked out the build (bropo-build-24) and ran the tests. I am running on python 3.10..

%> git pull %> git checkout bropo-build-24 %> make distclean %> ./configure --with-rave=..... %> make %> make test ...........................................................

Ran 59 tests in 5.202s

OK Objects created: 23691 Objects deleted: 23691 Objects pending: 0

I can't see that there are any breaking changes between the bropo-version involved so it should be ok to fetch the latest version. Only changes I can see is that ropo_options has been updated.

Den ons 10 apr. 2024 kl 13:28 skrev Milka-Radojevic-MF < @.***>:

Excellent. The corrected version were tested, right?

I forgot to mention that the error messages is related to the bropo-build-24, the version available at the time of building Cirrus composite production on Rocky Linux.

Should I clone the latest bropo?

— Reply to this email directly, view it on GitHub https://github.com/baltrad/bropo/issues/2#issuecomment-2047282513, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHWXQY3F45YE76M25C3GTFTY4UO7LAVCNFSM5EEK5V2KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBUG4ZDQMRVGEZQ . You are receiving this because you were mentioned.Message ID: @.***>

MilkaRadojevic commented 7 months ago

Thanks for running the test. We run Python 3.9.

Only changes I can see is that ropo_options has been updated.

Indeed, I could see difference when comparing the two builds 21 and 55. The config file ropo_options.xml only includes Finish and Swedish radars. Is there a default rule for other radars?

MilkaRadojevic commented 7 months ago

I got answer to my question. There is default threshold= defined within the config file.