Every single InMAP run I have done has resulted in trillions of deaths in 1 cell

[Natalia Gonzalez]

I have tried just about everything under the sun and still consistently get one problematic cell (the same one every time) that tells me trillions of people will die. I even tried running the nei2005 example case, with all the provided example data and the example config, and I still get the same issue. I re-projected all my shp files to match the InMAP projection, as suggested to me in another thread, but the issue persists. Not exactly sure where to go from here. Open to any and all advice! As of now, I am dropping that cell from my analysis, but I worry about the validity of the rest of the results given this strange behavior.

Thank you,

Natalia

[Natalia Gonzalez]

Just a follow up on this, I tried it in 2 different computers and got the same issue. I circled the problematic cell with an allcause of 4 trillion and deaths on the order of 17 million. It is nowhere near my input emissions (green dots). My question is, can I still trust the results despite this persistent error?

Thank you!

[Chris Tessum]

Hi Natalie,

This isn't an error that I've encountered before, so I'm not sure what would be causing the issue. If you include additional information about what input data you're using and how you are running the model, we might be able to help.

Best regards,

Chris

[Chris Tessum]

Interestingly, that grid cell might be the one that contains my house in Urbana-Champaign, IL, so I'd be interested in learning what's going on.

[Natalia Gonzalez]

Hi Chris, thank you so much for your response. Here is an example of one of my config, two input files, and outputs for one run, although no matter how I modified the config (even for small test cases) or the inputs, I get the same issue on 2 separate machines. 

https://drive.google.com/drive/folders/1vAl7Dw43L3iiGjAPvSLKsyAQLSKhS1bE?usp=sharing 

I tried uninstalling and re-installing InMAP, but the issue persists. Just not sure if dropping that cell is sufficient or if the results are invalidated all together. Thanks again! 

[Talor Gruenwald]

Hi Natalia, 

I have had this same issue. I believe the problem is stemming from an erroneous all-cause mortality rate for that grid cell. It appears to be some sort of an artifact from the InMAP run, but I'm not sure why it does this. To remedy this, what i've done is calculate the premature mortality figures manually outside of the inmap run using the PM2.5 concentrations and total population in the grid cell, swapping out the erroneous all-cause mortality rate in the grid cell for a national average all cause mortality rate in deaths per 100k. You can then use these figures to apply a concentration response function manually and calculate the premature mortality for that grid cell. 

I would be curious to hear from Chris Tessum as to why this may be occurring, however. 

Talor

--
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 visit https://groups.google.com/d/msgid/inmap-users/3ac6e464-4464-4997-953f-34f65a3f9fb6n%40googlegroups.com.

[Natalia Gonzalez]

Hi Talor,

Thanks for your reply. I have one clarification question. Did you manually calculate premature mortality for all cells or just the problematic one?

Best,

Natalia 

[Talor Gruenwald]

I did it for all grid cells.

To view this discussion visit https://groups.google.com/d/msgid/inmap-users/fa391d28-afd2-4235-81c8-419d6389f829n%40googlegroups.com.