davidfrantz / force-udf Goto Github PK

FORCE 3.9.7
I have two parameter files, one was generated by TSA module, the other was generated with UDF module. Both have the same specs, and point to the same python script. I specified the INDEX=NDVI, SENSOR = LND5,7,8 in both parameter files.

When I ran the python script with TSA prm file, the inarray (PIXEL) has shape (nDates, 1, 1, 1) which is expected
However, when I ran the same script with UDF prm file, the inarray has shape (nDates, 6, 1, 1) which I think 6 here is the 6 bands from Landsat data, which I did not want. Also, no matter what I specified in the INDEX, it always returns exactly 6 bands

Is this intended to have different behaviours for running UDF from different modules?

There seems to be a bug in the mowing detection python UDF that can cause no output when a date too early in the season is included:
davidfrantz/force#318 (reply in thread)

Apparently, the workaround is to use the DOY_RANGE parameters to mitigate this, but a proper fix might be the better solution.