You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I originally thought that there was only one missing trip in the analysis eval code, but it turns out that there are actually several. Even in the original master branch that I checked in as part of MobilityNet/mobilitynet-analysis-scripts@66545ae
I just didn't check the missing trips correctly
On the one hand, this is good because the trip segmentation on the two branches is the same, so we should expect to see the same results. On the other hand, we do need to check the data to see verify that we really didn't have location data to work with and missed the trip.
timeline
master
gis-branch
av_la
ios ucb-sdb-ios-2 HAHFDC v/s HAMFDC:HAHFDC_1MISSING TRIP: found 1, expected 2
ios ucb-sdb-ios-2 HAHFDC v/s HAMFDC:HAHFDC_1MISSING TRIP: found 1, expected 2
av_la
ios ucb-sdb-ios-3 HAHFDC v/s MAHFDC:MAHFDC_0MISSING TRIP: found 1, expected 2
ios ucb-sdb-ios-3 HAHFDC v/s MAHFDC:MAHFDC_0MISSING TRIP: found 1, expected 2
av_ucb
ios ucb-sdb-ios-2 MAMFDC v/s MAHFDC:MAMFDC_0MISSING TRIP: found 2, expected 3
ios ucb-sdb-ios-2 MAMFDC v/s MAHFDC:MAMFDC_0MISSING TRIP: found 2, expected 3
av_ucb
ios ucb-sdb-ios-2 MAMFDC v/s MAHFDC:MAMFDC_2MISSING TRIP: found 2, expected 3
ios ucb-sdb-ios-2 MAMFDC v/s MAHFDC:MAMFDC_2MISSING TRIP: found 2, expected 3
av_ucb
ios ucb-sdb-ios-2 MAMFDC v/s HAMFDC:MAMFDC_2MISSING TRIP: found 2, expected 3
ios ucb-sdb-ios-2 MAMFDC v/s HAMFDC:MAMFDC_2MISSING TRIP: found 2, expected 3
The text was updated successfully, but these errors were encountered:
I originally thought that there was only one missing trip in the analysis eval code, but it turns out that there are actually several. Even in the original master branch that I checked in as part of
MobilityNet/mobilitynet-analysis-scripts@66545ae
On the one hand, this is good because the trip segmentation on the two branches is the same, so we should expect to see the same results. On the other hand, we do need to check the data to see verify that we really didn't have location data to work with and missed the trip.
av_la
ios ucb-sdb-ios-2 HAHFDC v/s HAMFDC:HAHFDC_1
MISSING TRIP: found 1, expected 2
ios ucb-sdb-ios-2 HAHFDC v/s HAMFDC:HAHFDC_1
MISSING TRIP: found 1, expected 2
av_la
ios ucb-sdb-ios-3 HAHFDC v/s MAHFDC:MAHFDC_0
MISSING TRIP: found 1, expected 2
ios ucb-sdb-ios-3 HAHFDC v/s MAHFDC:MAHFDC_0
MISSING TRIP: found 1, expected 2
av_ucb
ios ucb-sdb-ios-2 MAMFDC v/s MAHFDC:MAMFDC_0
MISSING TRIP: found 2, expected 3
ios ucb-sdb-ios-2 MAMFDC v/s MAHFDC:MAMFDC_0
MISSING TRIP: found 2, expected 3
av_ucb
ios ucb-sdb-ios-2 MAMFDC v/s MAHFDC:MAMFDC_2
MISSING TRIP: found 2, expected 3
ios ucb-sdb-ios-2 MAMFDC v/s MAHFDC:MAMFDC_2
MISSING TRIP: found 2, expected 3
av_ucb
ios ucb-sdb-ios-2 MAMFDC v/s HAMFDC:MAMFDC_2
MISSING TRIP: found 2, expected 3
ios ucb-sdb-ios-2 MAMFDC v/s HAMFDC:MAMFDC_2
MISSING TRIP: found 2, expected 3
The text was updated successfully, but these errors were encountered: