Vital signs must have finite values - NaN is invalid about synthea HOT 5 CLOSED

Hey @arvindshmicrosoft, thanks for reporting this. I'm looking into it.

As far as the exception goes, that crashes the executor for the single patient. It should not impact the rest of the population.

from synthea.

@arvindshmicrosoft thanks for the update. The log for Wauwatosa, Wisconsin was especially helpful because it allowed me to reproduce the issue within a reasonable sized population.

The root of the issue is a method that converts BMI percentile into an actual BMI for an individual. For the case causing the issue in Wauwatosa, the individual has a BMI in the ~99.74th percentile. Given other parameters in the equation, this high value caused a component to flip from positive to negative, which causes the entire method to return NaN. The issue is somewhat rare because the code path also requires that the simulated individual undergoes successful weight loss in their late teenage years and then regress in weight management where their period of weight regression overlaps their 20th birthday. This is where the code switches from pediatric to adult weight management algorithms.

I should be able to put together a PR to fix this particular issue next week.

from synthea.

Hi @arvindshmicrosoft! I'm having a hard time reproducing this issue. Two questions:

1. Are you only seeing the NaN issue? I have seen a few other stack traces while running simulations, but not this one.
2. Could you run unzip -p synthea-with-dependencies.jar META-INF/MANIFEST.MF and put the output in a comment? I want to make sure we are working from the exact same jar file.

from synthea.

Hi @arvindshmicrosoft! I'm having a hard time reproducing this issue. Two questions:

1. Are you only seeing the NaN issue? I have seen a few other stack traces while running simulations, but not this one.
2. Could you run unzip -p synthea-with-dependencies.jar META-INF/MANIFEST.MF and put the output in a comment? I want to make sure we are working from the exact same jar file.

Sure, here we go @eedrummer. Note that I have built from source - commit 6192ed7 (latest as of 2023-10-07).

Manifest-Version: 1.0
Main-Class: App
Build-Timestamp: 2023-10-06T21:17:14.165+0000
Build-Version:
Created-By: Gradle 8.2.1
Build-Jdk: 11.0.20 (Red Hat, Inc. 11.0.20+8-LTS)
Build-OS: Linux amd64 4.18.0-477.27.1.el8_8.x86_64

Unfortunately, I don't seem to have the old logs available. I found some other runs - where the same exception is reported. There are multiple cities for which this was observed, but as a representative example, I am sharing the logs for Austin, TX. You'll notice some other exceptions in this as well, but there are other cities with just the setVitalSign exception, like this one for Wauwatosa, WI.

from synthea.

@eedrummer Thank you for fixing this issue. I no longer see this issue with the current code.

from synthea.