Hello,
When we try to run a custom job for the “S4C L4C Agricultural Practices” processor, we are getting an error and I’m not sure why. The full output of the error is below:
==============
ERROR: No value associated to the parameter : “il”, invalid number of values 0
ERROR: Troubles loading parameter, please check your line argument…
This is the Markers1CsvMerge application, version 5.0.0
Computes statistics on a training polygon set.
Complete documentation: http://www.orfeo-toolbox.org/Applications/Markers1CsvMerge.html
Parameters:
-progress Report progress
-il Input Images or file containing the list (mandatory)
-out Output file (mandatory)
-sep CSV Separator (optional, off by default)
-ram Available RAM (Mb) (optional, off by default, default value is 128)
-inxml Load otb application from xml file (optional, off by default)
Examples:
otbcli_Markers1CsvMerge -in support_image.tif -out /path/to/output/
==============
I suppose the real question is how do we check/confirm what the line parameters are? Is this something we supply and could have incorrect somewhere - or is this hardcoded by Sen2Cap?
Any advice would be greatly appreciated.
Thanks
Hello,
The error might be due to the fact that you tries to run a markers DB custom job without having uploaded an LPIS for the year these products belong to. The error is a little bit confusing and we’ll try to correct it in the next future as the error should be given during request creation and not later at job execution.
Actually what is happening in your case, as you don’t have the parcels uploaded or products outside the year of the loaded LPIS they are removed from your request as not “processable”. This can be seen in the logs of the sen2agri-orchestrator where you should have in this case something like “MDB1: Product X not processed as there is no LPIS for product year Y”.
Hope this helps.
Best regards,
Cosmin
Good morning,
some time ago, we started having many L4C jobs triggered with some continuity, and failing:
The few steps within the job fail with the same error as written in the initial post of this thread.
Since the new products being pre-processed are of year 2020, but we have only the LPIS for 2021, I wonder if the L4C jobs are somehow triggered by the pre-processing and then fail because of the missing LPIS for 2020?
In any case, is it possible to prevent those jobs from being triggered?
Best regards,
Emanuele
Having the exact same issue as Emanuele. However, we did not attempt to launch it without an LPIS, so there might be another cause to it. As to what - that’s anyone’s guess. 
Hello,
To avoid triggering of data extraction for the L4C processor, you can set in config table the key “processor.s4c_l4c.nrt_data_extr_enabled” to false:
psql -U admin sen4cap -c "update config set value = false where key = ‘processor.s4c_l4c.nrt_data_extr_enabled’ "
Hope this helps.
Best regards,
Cosmin
Hello,
thank you for your advice, it worked!
Best regards,
Emanuele
