Open hjabbot opened 5 months ago
Currently, all NaN's in a mesh are set to 0's by the vessel performance modeller.
With the refactoring of the route planner, we plan to remove this from the vessel performance modeller and have them handled more gracefully by the route planner. This work is still ongoing
Moving here from project repo #83.
This could go into MeshiPhi, but I personally think that NaN's are perfectly valid in meshes, so anything downstream should handle NaN's gracefully. Issue is NaNs and Infs aren't natively supported by the JSON schema so strictly speaking they shouldn't be in the output of MeshiPhi meshes, but it seems dangerous to equate NaNs to a real value.