Hi @dmitry ,
Sorry for the late response here. I know that this type of capability of integrating CFD results is in high demand and I’m working towards exposing it. In fact, this ladybug-comfort mtx utci command that’s being run under the hood of the UTCI recipe already has an input for --air-speed-mtx, which is meant to take an input exactly like what you have there. I just have to expose it on the recipe inputs but this presents some questions.
For example, I’ve been trying to find the best way to handle cases like multiple sensor grids. Should I expect an input of multiple air speed CSV files in this case? So you have one CSV file per sensor grid? If you have any thoughts on this, please feel to share them.
In the meantime, I can give you a workaround for postprocessing the UTCI comfort map results in Grasshopper to include your CFD air speeds. I just added a component that can parse the raw MRT results from the comfort map into Grasshopper:
So you can use the Ladybug “UTCI Comfort” component to post-process the raw MRT results as you wish:
outdoor_comfort_under_a_tree_postprocess.gh (127.5 KB)
You’ll just have to format your CFD wind speeds as a list of data collections in order to plug them into the _wind_vel_ input of the UTCI component. It’s by no means optimized for speed or scale-ability but at least you can do it.