" + "

{{message}}" + "

" }, {"view_id": "choice"}, {"view_id": "html", "html_template": "

" + "" + "EUP Tree" + "

" }, { "view_id": "html", "html_template": "" + "

" + "" + "Ambig" + "

" + "

" + "" + "Contextual" + "

" + "

" + "" + "Multi-EUP" + "

" + "

" + "" + "Partial" + "

" + "

" + "" + "Side Conversation" + "

" + "

" + "" + "STT Error" + "

" }, {"view_id": "text_input", "field_label": "Proposed EUP(s)", "field_id": "proposedEUP"}, {"view_id": "text_input", "field_label": "notes"} ] def add_options( stream, label_field="eup", choices=DIFFERENT_EUP ) -> Generator[Dict, None, None]: """ Convert each line in the ``stream`` to a ``task`` with a text and an options field :param stream: the input stream :param label_field: key; defaults to "label" :param choices: the different choices :yield: a task Dict with text and options """ for line in stream: if label_field in line: options = json.loads(line[label_field]) else: options = [] for word in (options + choices): if word not in options: options.append(word) task = { "eup": line["eup"], "message": line["message"], "ambig": False, "contextual": False, "multi": False, "partial": False, "side_conversation": False, "stt_error": False, "options": [ {"id": o, "deployment": o, "prompt": o, "text": o} for o in options ] } yield task @prodigy.recipe( "eup-corpus-validation-with-options", dataset=("The dataset to save to", "positional", None, str), file_path=("Path to texts", "positional", None, str), label_field=("Label to use for the accept task", "option", "f", str), choice_field=("Choices to add to the input", "option", "c", str) ) def custom_labels(dataset, file_path, label_field, choice_field): """ Annotate the text with labels from the list from the ``label_field`` in the input file. Augmented with choices from ``choice_field``. """ blocks = UNLIMITED_ROWS stream = JSONL(file_path) stream = add_options(stream) # add options to each task javascript = """ // Set ambig to false by default prodigy.update({ ambig: false }); function updateAmbig() { prodigy.update({ ambig: document.getElementById('ambig').checked }); } document.addEventListener('prodigyanswer', (event) => { // Reset ambig to false prodigy.update({ ambig: false }); document.getElementById('ambig').checked = false; }); // Set contextual to false by default prodigy.update({ contextual: false }); function updateContextual() { prodigy.update({ contextual: document.getElementById('contextual').checked }); } document.addEventListener('prodigyanswer', (event) => { // Reset contextual to false prodigy.update({ contextual: false }); document.getElementById('contextual').checked = false; }); // Set multi to false by default prodigy.update({ multi: false }); function updateMulti() { prodigy.update({ multi: document.getElementById('multi').checked }); } document.addEventListener('prodigyanswer', (event) => { // Reset multi to false prodigy.update({ multi: false }); document.getElementById('multi').checked = false; }); // Set partial to false by default prodigy.update({ partial: false }); function updatePartial() { prodigy.update({ partial: document.getElementById('partial').checked }); } document.addEventListener('prodigyanswer', (event) => { // Reset partial to false prodigy.update({ partial: false }); document.getElementById('partial').checked = false; }); // Set side_conversation to false by default prodigy.update({ side_conversation: false }); function updateSideConversation() { prodigy.update({ side_conversation: document.getElementById('side_conversation').checked }); } document.addEventListener('prodigyanswer', (event) => { // Reset side_conversation to false prodigy.update({ side_conversation: false }); document.getElementById('side_conversation').checked = false; }); // Set stt_error to false by default prodigy.update({ stt_error: false }); function updateSttError() { prodigy.update({ stt_error: document.getElementById('stt_error').checked }); } document.addEventListener('prodigyanswer', (event) => { // Reset stt_error to false prodigy.update({ stt_error: false }); document.getElementById('stt_error').checked = false; }); """ return { "dataset": dataset, "view_id": "blocks", "stream": list(stream), "config": { "blocks": blocks, "javascript": javascript } } ``` Running this: ```python PRODIGY_ALLOWED_SESSIONS=cheyanne prodigy eup-corpus-validation-with-options eup_val_options_install_test examples.jsonl -F eup_corpus_validation_with_options.py ``` Yields this: ```python the following arguments are required: --label-field, --choice-field ``` This seems to be the same error message mentioned [here](https://support.prodi.gy/t/label-field-and-choice-field-error-with-v-1-14-0/6809/9). So I'll dive in. The error message seems sound to me looking at the recipe declaration. ```python @prodigy.recipe( "eup-corpus-validation-with-options", dataset=("The dataset to save to", "positional", None, str), file_path=("Path to texts", "positional", None, str), label_field=("Label to use for the accept task", "option", "f", str), choice_field=("Choices to add to the input", "option", "c", str) ) def custom_labels(dataset, file_path, label_field, choice_field): """ Annotate the text with labels from the list from the ``label_field`` in the input file. Augmented with choices from ``choice_field``. """ ``` We can see `label_field` in the decorator and this isn't referenced in the command line. But we aren't passing `--label-field` from the command line. So that would explain the error message. But my editor also suggests that `label_field` and `choice_field` aren't used in the recipe at all either. ![CleanShot 2023-10-31 at 10.53.54](https://us1.discourse-cdn.com/flex020/uploads/prodigy/original/2X/7/787273f32f9d37f82db5bb81c906b0e3c954d305.png) Do tell if I'm glancing over something, but shouldn't those two inputs be removed? When I remove them I get other issues, but I'd like to make sure what the intention is here before moving on. ---

**Author:** ![cheyanneb](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/cheyanneb/32/2409_2.png) [@cheyanneb](https://support.prodi.gy/u/cheyanneb)\ **Post date:** [October 31, 2023, 1:50pm UTC](https://support.prodi.gy/t/label-field-and-choice-field-error-with-v-1-14-0/6809/16 "2023-10-31T13:50:58Z")

I removed `choice_field` and that error is now gone. Yes, that wasn't being used and should have been removed. `label_field`: labels are imported from the `.jsonl` file. If I use the following command with dummy labels when I call the recipe, I can launch the recipe, but this recipe is basically validating our intent model: it's taking the top three results from our model (in the `.jsonl` dataset) and providing them as choices to the annotator along with two custom options (a different intent`, an `intent that doesn't exist`) that I'm importing from a utils file. ```python (prodigy) cheyannebaird@Cheyannes-MBP:~/posh/annotation-service$ PRODIGY_ALLOWED_SESSIONS=cheyanne prodigy eup-corpus-validation-with-options eup_val_options_install_test /Users/cheyannebaird/posh/eup_corpus/eup_task_april2023/final_final/eup_low_scoring_data_v1.jsonl -F /Users/cheyannebaird/posh/annotation-service/src/annotator/recipes/eup_corpus_validation_with_options.py --label foo,bar ⚠ Prodigy automatically assigned an input/task hash because it was missing. This automatic hashing will be deprecated as of Prodigy v2 because it can lead to unwanted duplicates in custom recipes if the examples deviate from the default assumptions. More information can found on the docs: https://prodi.gy/docs/api-components#set_hashes ✨ Starting the web server at http://localhost:8080 ... Open the app in your browser and start annotating! ``` ---

**Author:** ![koaning](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/koaning/32/230_2.png) [@koaning](https://support.prodi.gy/u/koaning)\ **Post date:** [November 1, 2023, 9:28am UTC](https://support.prodi.gy/t/label-field-and-choice-field-error-with-v-1-14-0/6809/17 "2023-11-01T09:28:45Z")

Just to check, does that mean that you're no longer blocked? ---

**Author:** ![cheyanneb](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/cheyanneb/32/2409_2.png) [@cheyanneb](https://support.prodi.gy/u/cheyanneb)\ **Post date:** [November 2, 2023, 12:51pm UTC](https://support.prodi.gy/t/label-field-and-choice-field-error-with-v-1-14-0/6809/18 "2023-11-02T12:51:59Z")

I may have to adjust our task definitions to add dummy labels when using the recipes that are throwing this error -- so far only span, review and NER recipes are not throwing this error because I'm explicitly defining a label set. We create a task definition that is tied to a specific dataset, and if the dataset contains the labels or the task involves classification, then I'm not calling the labels directly in the task definition. Since we're now getting this label error in the latest update, I am going to test adding dummy labels to the task definition to see if that's a workaround for us. ---

**Author:** ![koaning](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/koaning/32/230_2.png) [@koaning](https://support.prodi.gy/u/koaning)\ **Post date:** [November 2, 2023, 2:05pm UTC](https://support.prodi.gy/t/label-field-and-choice-field-error-with-v-1-14-0/6809/19 "2023-11-02T14:05:38Z")

Ok! Let me know if you have something reproducible that I can check out locally with a bug in it. I'm eager to fix any bugs, but I will need to be able to run the same code as you to make sure I'm adressing the issue correctly. Let me know! ---

**Author:** ![cheyanneb](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/cheyanneb/32/2409_2.png) [@cheyanneb](https://support.prodi.gy/u/cheyanneb)\ **Post date:** [November 2, 2023, 5:29pm UTC](https://support.prodi.gy/t/label-field-and-choice-field-error-with-v-1-14-0/6809/20 "2023-11-02T17:29:26Z")

I think I figured out the issue, and I was able to get the recipe to run without dummy labels. I had another `label_field` declared that was unused. Removed it, and now we're good! [Next page](https://support.prodi.gy/t/label-field-and-choice-field-error-with-v-1-14-0/6809.md?page=2)