David Youssefi

Hi @lionlai1989, I think your issue is due to instabilities in dask mode. I would recommend you using multiprocessing mode of compute_dsm pipeline : ``` cars compute_dsm --mode mp --nb_workers...

Hi @lionlai1989, with the new API, you have to provide all the arguments through the config.json file ``` { "inputs": { "sensors": { "one": { "image": "Duesseldorf/IMG_PHR1A_P_001/IMG_PHR1A_P_201807271102180_SEN_3385144101-1_R1C1.JP2", "geomodel": "Duesseldorf/IMG_PHR1A_P_001/RPC_PHR1A_P_201807271102180_SEN_3385144101-1.XML", "no_data":...

Hi @lionlai1989, Most of the people on the team are on vacation or at FOSS4G this week (me included), so we will analyse your issue next week. We will keep...

Hi @lionlai1989, https://github.com/CNES/cars/commit/5dd71e60fa8b0006b2a09ce11edc101799be3982 should fix the problem. Can you "docker pull" cnes/cars:0.5.1 and try again ? Thanks in advance, David

Hello @GuDesp, thanks for reporting the problem here. Please could you send us your Config.json file and your data ? Thank you in advance for your answer

Hello @GuDesp, sorry for delay too. I found the solution : it seems that the Orfeo Toolbox that we use for read images does not manage to read the model....

PS : Here's the screenshot of the result : 

Hello @GuDesp, have you tried with the recommendations ? Can we close the issue ? Best regard, David

I close this issue : @GuDesp : if you don't manage to obtain your DSM, you can re open it. Best regard, David

Hi @zoepapirer, We are currently experiencing some difficulties with the disparity intervals to be explored. We're releasing version 0.7.4 with local disparity intervals which may help solve the problem. I'll...