Kalum Ost

Hello: the discussion on issue #298 should help solve your problem. Let me know if that doesn't help: hopefully we can work through it

Can you please give us the use-case that raises said error (is it an update, creation, or retrieval)? I suspect that whats happening is you're trying to update the value...

Update; changes allowing null updates have been made, and are available in v0.0.13 of rest-meets-djongo. Hopefully that fixes the issue

Are you passing in a Note without wrapping it in a list? Seems like the most likely culprit here. (I'll look into adding a more informative error message for that...

From the Django [`bulk_create()` documentation](https://docs.djangoproject.com/en/2.2/ref/models/querysets/#bulk-create): > If the model’s primary key is an AutoField it does not retrieve and set the primary key attribute, as save() does, unless the database...

Agree; might it be worth making `SCTArgumentParser` have a subclass specifically for DeepSeg then?

Going to second this, as now changes to the CLI argument parsing (which should have a substantial impact on performance in the slightest) are failing too. See #4819 for details...

To be discussed at next meeting (March 13th, 2024); if the plan I propose is acceptable, will assign myself to this and proceed with developing these benchmarks.

After the aforementioned meeting, I will wait on implementing this until the rest of the lab has a chance to propose any other aspects of a standard SCT run they...

Update on this front; the repository [here](https://github.com/SomeoneInParticular/sct_timings) has been made specifically to address this. I'm just adding the final touches (namely CI, plot generation, and moving it under the SCT...