-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
⁉️ When pipeline is re-run for this user, it doesn't generate cleaned objects #1071
Comments
The assertion errors are validation or quality control checks on the pipeline. They are turned on by default in dev versions so we can see what is going wrong. In this case, it is almost certainly
But if you would like to ignore that for now since it is not a section you worked on, you can turn off the various assertion errors in |
In that case, it should not affect production right? |
It doesn't have any trips on production because I upgraded DFC fermata to the version with the BLE matching, and reset the pipeline for all users so that the trips and sections would be re-created and we could generate a snapshot with the correct data format for public dashboard testing. The trips should be showing up soon, or any errors will be in the intake pipeline logs. |
Ah I see, I thought it would have finished processing by now |
Circling back to this and confirming that I was able to get my trips to process locally by turning off the assertion errors. I'd still like to know why my sections were considered "invalid" (I've also seen logs saying "This is messed up segment. Investigate further while processing section, skipping...") |
Using
e-mission-server
master
Load the Apr 24 dump for
dfc-fermata
Inspect the cleaned objects for my opcode:
Output:
Reset pipeline for user
./e-mission-py.bash bin/reset_pipeline.py -e nrelop_dfc-fermata_test_████
Run pipeline for user
./e-mission-py.bash bin/debug/intake_single_user.py -e nrelop_dfc-fermata_test_████
"Cleaning and resampling failed"
Now we have no cleaned objects (and thus no confirmed or composite objects)
The text was updated successfully, but these errors were encountered: