Open tdivoll opened 10 months ago
@danielmwatkins, have you gotten this error at all when running the SOIT script?
I haven’t, what are the case settings you were trying?-DanielOn Jan 19, 2024, at 13:07, Timothy Divoll @.***> wrote: @danielmwatkins, have you gotten this error at all when running the SOIT script?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
I seem to get it when running SOIT via Cylc on Oscar with the bering_sea
set from the sample locations. @cpaniaguam reminded me that there is some discussion of this in the SOIT repo:.
I think it's just an issue with certain dates and certain overpass times.
I seem to get it when running SOIT via Cylc on Oscar with the
bering_sea
set from the sample locations. @cpaniaguam reminded me that there is some discussion of this in the SOIT repo:. I think it's just an issue with certain dates and certain overpass times.
It could also be certain combos of lat/lon pairs.
location: bering_strait center_lat: 65 center_lon: -170 top_left_lat: 55.92827 top_left_lon: -172.77869 lower_right_lat: 74.25843 lower_right_lon: -163.83708 left_x: -3002871.001 right_x: -1502871.001 lower_y: 827477.2577 top_y: 2327477.258 startdate: 2020-09-04 enddate: 2020-09-07
When running SOIT from a task and using the Docker image for software, getting an error: