SR Matrices Python Error: Job has reached the specified backoff limit?

Lino Sanchez

unread,

Oct 25, 2021, 3:49:08 PM10/25/21

to inmap-users

Hello,

I am trying to go through the InMAP Source-Receptor Matrices python tutorial from here: https://www.inmap.run/blog/2019/04/20/sr/

and encountered an error message that I am having trouble understand. I am just trying to get the tutorial working, running all of the code exactly as it appears in the tutorial, using the same provided EPA emissions data. Everything worked fine, until I entered the following code (using Jupyter Notebook):

This produced the following error message:

I was excited to see that the model was running, showing elapsed times readings, but I am not sure why the model failed and how I can fix this. I am just trying to get the intended InMAP output that was shown in the tutorial. Has anyone experienced this error before? I would really appreciate any help in solving this issue!

Thanks!

Lino

Chris Tessum

unread,

Nov 3, 2021, 1:55:32 PM11/3/21

to inmap-users

Hi Lino,

I tried it just now, and it works for me. Perhaps try using the most recent version of the run_sr.py file: https://raw.githubusercontent.com/spatialmodel/inmap/master/website/static/blog/2019-04-20-sr/sr_util.py

If that still doesn't work, could you let me know what operating system you are using?

Chris

Lino Sanchez

unread,

Nov 12, 2021, 8:14:37 PM11/12/21

to inmap-users

Hi Chris,

Thanks for your reply. I tried using the updated run_sr.py file you linked to, but encountered the same issue, with this time making it to 461 seconds before I get that message telling me the simulation failed.

I am using Microsoft Windows 10 Home for my operating system.

Thanks,

Lino

Paige Weber

unread,

Jan 6, 2022, 11:28:07 AM1/6/22

to inmap-users

Hi Chris, Lino, and All, Apologies if this note is going through twice (re-sending as it looks like my last message didn't go through). I am wondering if anyone else has encountered this backoff limit issue and if there is any work around? I get the same error, "Job has reached the specified backoff limit" after 359 seconds. I'm working on MacOS BigSur v11.4. Appreciate any suggestions for this!

Best, Paige

Lino Sanchez

unread,

Jan 6, 2022, 1:57:19 PM1/6/22

to inmap-users

Hi Paige,

Hmmm I am trying to remember what solved this issue for me, but if I recall it was an issue with my Jupyter Notebook installation, and so I might suggest reinstalling or updating Jupyter Notebook. For me, I was running Jupyter Notebook from an Anaconda environment, and then once I installed Jupyter Notebook just via pip, I noticed a lot of issues I had previously seen were resolved. Either that or there might be some package dependency you are missing with geopandas. That's all I can think of, but would love to hear from someone who knows python way better than I do.

Good luck!

Lino

Paige Weber

unread,

Jan 6, 2022, 9:34:24 PM1/6/22

to Lino Sanchez, inmap-users

Thanks for the reply, Lino! I tried re-installing Jupyter with pip, and I am still getting the same backoff limit error. Look forward to hearing if anyone else has gotten this error and has any other successful work arounds to suggest.

Thanks, Paige

--
You received this message because you are subscribed to the Google Groups "inmap-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to inmap-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/inmap-users/fab9ba37-b4c2-4c9c-9eff-50d709c0d7fdn%40googlegroups.com.

Chris Tessum

unread,

Jan 31, 2022, 2:40:46 PM1/31/22

to inmap-users

"Job has reached the specified backoff limit" just means that the cloud server tried to run the simulation a bunch of times and they all failed. Sometimes simulations will fail because the cloud server is overwhelmed with too many requested simulations. Sometimes there is a problem with the cloud server, which I will try to resolve if I'm aware of it. Sometimes there is a configuration issue. Based on the information I can see as an administrator of the server, it seems like a common issue is incorrectly specifying the version of InMAP that you would like to use. (A good one to use currently would be "v1.9.0", with the "v" included, but if you you're using the file "run_sr.py" you can just download the most recent version.)

Unfortunately, not all of the information currently gets conveyed back across the internet to describe what the error was that actually happened in a given case. Apologies for that. Contributions are welcome to help fix that problem!

Best regards,

Chris

Graeme Peterson

unread,

Sep 1, 2022, 9:34:56 AM9/1/22

to inmap-users

Hi all,

Thanks for the helpful previous messages on here. I ran into the same error ("job has reached the specified backup limit") this morning after 795 seconds. There was also an accompanying message that appeared several times during the attempted run that said: "b'rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"\n'", which I think was also mentioned in this other thread: https://groups.google.com/g/inmap-users/c/UjZkIBA3POU.

I'm running this on macOS Big Sur 11.6.8.

Is it possible that there are too many requested simulations at the moment, as was the case in some of the other instances where this error occurred? Or does this seem like it is a problem on my end? Thank you very much for your time and your help.