Marek Horst

We should drop the `ISLookupServiceBasedConceptImporter` along with the whole `ISLookupFacade` stack including tests and workflow definitions.

Adding the following line: ``` log4j.logger.eu.dnetlib.iis.wf.affmatching.match.voter=TRACE ``` in the `iis-wf/iis-wf-affmatching/src/test/resources/log4j.properties` file will solve that issue. It will be solved assuming the `.classpath` file created for Eclipse environment within the `iis-wf-affmatching`...

I proved this to be working in a local environment it just needs to be decided if it should be a default configuration. One obvious drawback is having test logs...

One viable solution is to replicate the `finally` block execution on the oozie workflow definition level, similarly to the metadata extraction workflow where lock management logic was handled solely within...

@lfoppiano, thank you for your reply, I really appreciate your help! Let me comment your remarks. > One example of fallback on CPU is this: I just scanned my logs...

Hi @lfoppiano > Can you shell into the container? and try to check whether you can access the GPUs from within? Yes, after I shell into the apptainer with: ```...

I managed to put everything together. After integrating Grobid with metadata extraction and setting up the whole workflow the job fails due to the following issue: ``` 2025-03-21 13:36:33,338 FATAL...

> Possible solutions: > > * loading user dependencies first (it should be possible also with MapReduce) In the end this turned out to be enough by simply defining the...