Sebastian Husch Lee

How restrictive would this be for something like Molpro or Psi4? Would allowing the user to write custom inputs (handled through something like Jinja) go against the QCArchive framework?

That sounds reasonable to me. For my projects (including my MolSSI Seed project) I'll probably need the ability to express a complicated input file, but then parse fairly standard items...

Yes, I think so and deletion is also recommended in the Discord discussion. @avijit9 Would you be willing to open a PR for this?

Hi @ZanSara I know this is a fairly old issue, but I'm currently working on expanding the utility of the EntityExtractor in this issue: https://github.com/deepset-ai/haystack/issues/2969 and I think I have...

> @sjrl this looks great! Is it fully compatible with the run and run_batch results of the previous EntityExtractor? Yes! I checked that the output between the two methods was...

@vblagoje Should I label this PR with breaking change since I've changed the default behavior of the `EntityExtractor`? Specifically, I've changed the default model and I have changed the default...

> @sjrl it's breaking only if we change the API, not the implementation. Would I be able to run a script (or a pipeline) written for Haystack 1.8.0 without touching...

> It seems that the predictions of the node are a bit off, as they are very long. So the conversion of the labels should be checked again. Converted back...

Hey, @vblagoje I would appreciate a review of the new code since your last review. I wrote a description of the new changes under the **Update:** header in the PR...

When running the NER node (and the unit tests) this warning from HF appears ```python Process finished with exit code 0 PASSED [100%]huggingface/tokenizers: The current process just got forked, after...