-
Notifications
You must be signed in to change notification settings - Fork 3
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
## PY29 - Moved to keep #30 clean #36
Comments
Hmmm, that's really strange. It shows up in the .csv, so maybe Curricular Analytics is doing something to it? Deep dive time (after I get lunch - edit I'm back now, found out why it happens - uploaded version has some missing prereq links, generated doesn't miss. writing up now). |
Yeah, that's roughly it. The catalog explicitly lists 100A, 110A and 4E as pre-reqs for 130A. The .csv for the uploaded version lists all three, but it also lists 4E as a direct pre-req of 100A and 110A. The catalog disagrees - 4E is not a pre-req of 100A or 110A. So, in the uploaded version 4E folds into being a direct pre-req of 100A and 110A, which are in turn direct pre-reqs of 130A. That is incorrect. The correct form is the generated form, where 4E is not a prereq of either, so it is a direct pre-req of 130A. |
Yeah, no idea but it matches with the online plan generator, so it's totally fine. |
Seems like the generated version is correct so I'll close this |
PY29
Uploaded, generated
The prerequisites do be looking quite dense
Interestingly, the uploaded version lists math 20a as what seems to be a corequisite of math 18, while the generated version says math 20a is a prerequisite. The generated version isn't wrong because math 20a satisfies math 18's prerequisites. However, in practice, because we assume students have satisfied pre-calc, which is also an alternative prereq of math 18, students should be able to take 20a and 18 in the same quarter. This ultimately puts math 18 in a later column in the curriculum, but shouldn't affect degree plans I think.⚠️
The uploaded version lists phys 4e as a prereq for phys 110a (in addition to math 20e), which makes it one column longer than the generated version. The generated version instead has phys 4d.
Interestingly, PHYS 4E isn't even a prereq for PHYS 110A:
so the uploaded version appears to be wrong.
Only the uploaded version lists math 20e as a prereq for phys 105a, but the generated version doesn't. I'm not sure why. I'll have to look into this. 🚩
Only the uploaded version lists math20e as a prereq for phys 100a. The generated version doesn't because math 20d already does
Only the generated version lists phys 4e as a prereq for phys 130a. I don't know why the uploaded version doesn't, but this might have to do with it listing phys 110a, another prereq of 130a, as requiring phys 4e.
Only the generated version lists math 20e as a prereq for phys 4d. This is correct.
Revelle
that's a lot of lines
For some reason, PHYS 2DL is in term 6 in the uploaded version but term 7 in the generated version.
More significantly, the updated version uses a corequisite arrow from math 20a to math 18 while the generated version uses a prerequisite arrow, despite the two courses being in the same quarter. Curricular Analytics renders this fine, but I think this should be changed: 🚩
When editing the degree plan directly (by enabling editing mode, which I used to reorder the courses within quarters), math 18 pops ahead of 20a and can't be placed in the same quarter. This leads to somewhat buggy but not catastrophic behavior when you try to drag math 20a because it shows up to the left of the entire plan off the screen. Fortunately it snaps back to term 1 when you let go.
It probably also affects the complexity score (since it might think that math 20a blocks more courses than it actually should normally)
Since I don't think math 18 and 20a are listed as prereqs with concurrent enrollment enabled (I'd have to check this), to fix this, I could check if a prerequisite is in the same or later quarter and mark it as a corequisite instead
Originally posted by @SheepTester in #30 (comment)
The text was updated successfully, but these errors were encountered: