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
When creating degree plans, I noticed that several of the courses in the plan were displaying delay factors that appeared to be incorrect. Included in attachments are screenshots of the erroneous delay factors, as well as a word document containing code that can be used to replicate the display for errors 1 through 3.
Currently using CurricularAnalytics v0.6.6 and Julia v1.2.0, though this error was also occurring on CurricularAnalytics v0.6.3.
(Notes: Correct value for photo 1's delay factor is 7 (displayed as 4), photo 2's factor should be 7 (displayed as 5), photo 3 should be 8 (displayed as 6), photo 4 should be 6 (displayed as 5))
Please let me know if you need any more information regarding the bug, and thank you for your help!
Thanks so much for bringing this bug to our attention. There should be tests built in that check the metrics are being calculated correctly, but clearly at the least the visualization isn't showing the correct numbers. We will work to correct this as soon as possible.
When creating degree plans, I noticed that several of the courses in the plan were displaying delay factors that appeared to be incorrect. Included in attachments are screenshots of the erroneous delay factors, as well as a word document containing code that can be used to replicate the display for errors 1 through 3.
Currently using CurricularAnalytics v0.6.6 and Julia v1.2.0, though this error was also occurring on CurricularAnalytics v0.6.3.
(Notes: Correct value for photo 1's delay factor is 7 (displayed as 4), photo 2's factor should be 7 (displayed as 5), photo 3 should be 8 (displayed as 6), photo 4 should be 6 (displayed as 5))
Please let me know if you need any more information regarding the bug, and thank you for your help!
ENME Curricular Analytics Code.docx
The text was updated successfully, but these errors were encountered: