This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 63%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHJ%3C/text%3E%3C/svg%3E)
I am experiencing issues with the C# training p2 module, found at https://learn.microsoft.com/en-us/training/modules/guided-project-arrays-iteration-selection/5-exercise-implement-selection-statements. In this exercise, the variable sumAssignemtScores is set to int type, which causes inaccurate and wrong output when calculating scores that have a 10% influence on the final score. I think it should be type of decimal. Can someone help? This question is related to the following Learning Module
Thanks for posting your question in the Microsoft Q&A forum.
sumAssignmentScores originates from studentScores, both of which are integers. However, there are instances where a floating-point result is required from this value. In such cases, only the resulting value is converted. For instance, when calculating the currentStudentGrade.
Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 11%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPM%3C/text%3E%3C/svg%3E)
Thank you for reaching out to Microsoft Q & A forum.
Thank you for raising this concern. You're absolutely correct in noting that using the int data type for the variable sumAssignmentScores can lead to inaccuracies, especially when calculating scores that have a 10% influence on the final grade. This is because integer division truncates any decimal part, resulting in a loss of precision.
While the current implementation may seem to produce correct output for the provided data, it's essential to consider its limitations, particularly regarding the calculation of extra credit scores. In scenarios where extra credit scores significantly impact the final grade, relying on integer division could indeed result in inaccurate grading.
However, it's important to note that changing the data type of sumAssignmentScores to double might not be necessary in all cases. Using double introduces floating-point arithmetic, which could potentially introduce rounding errors or other issues.
Instead, we can address this concern by ensuring that the calculation involving sumAssignmentScores maintains precision. This can be achieved by explicitly casting the integer division operation to a floating-point type before performing the calculation. For example:
currentStudentGrade = (double)sumAssignmentScores / examAssignments;
By making this adjustment, we preserve the accuracy of the calculation without necessarily changing the data type of sumAssignmentScores. This approach maintains the integrity of the existing code while addressing the issue of precision loss in the calculation of student grades.
If you encounter any future issues, please feel free to contact us, and we will be pleased to assist you further.
If you have found the answer provided to be helpful, please click on the "Accept answer/Upvote" button so that it is useful for other members in the Microsoft Q&A community.
Thank you.
Thank you for your response; however, I believe I may not have explained the problem clearly.
// initialize/reset the sum of scored assignments
int sumAssignmentScores = 0;
// initialize/reset the calculated average of exam + extra credit scores
decimal currentStudentGrade = 0;
// initialize/reset a counter for the number of assignment
int gradedAssignments = 0;
// loop through the scores array and complete calculations for currentStudent
foreach (int score in studentScores)
{
// increment the assignment counter
gradedAssignments += 1;
if (gradedAssignments <= examAssignments)
// add the exam score to the sum
sumAssignmentScores += score;
else
// add the extra credit points to the sum - bonus points equal to 10% of an exam score
sumAssignmentScores += score / 10;
}
currentStudentGrade = (decimal)(sumAssignmentScores) / examAssignments;
The issue arises because the 'sumAssignmentScores' variable is defined as an integer. However, in the 'else' section, when calculating extra credit points, the scores are divided by 10 and then assigned to this variable. This is problematic because although 'sumAssignmentScores' is later cast to a decimal when calculating the 'currentStudentGrade' variable, the extra credits have already been incorrectly calculated.
int[] sophiaScores = new int[] { 90, 86, 87, 98, 100, 94, 90 };
int[] andrewScores = new int[] { 92, 89, 81, 96, 90, 89 };
int[] emmaScores = new int[] { 90, 85, 87, 98, 68, 89, 89, 89 };
int[] loganScores = new int[] { 90, 95, 87, 88, 96, 96 };
Extra credit points are divided by 10 and then added to an integer variable, which means all decimal points are lost. This is particularly significant for students whose exam scores are low but have high extra credit, as this issue can alter their total grade by one point or more.
Thank you for your time and patience.
I apologize for any confusion caused by my previous response. I've revised my answer, and I hope this resolves the issue. If you encounter any further difficulties in the future, please don't hesitate to ask for assistance. We are here to help you further and ensure a smooth resolution to any problems you may encounter. Your satisfaction and understanding are our priorities, and we remain committed to providing the support you need.
Hi @Pradeep M ,
Thank you for your time.
I've noticed that the problem is addressed in the following lesson of this chapter. I am seeking corrections for this particular lesson.
Hi Hamidreza Jorjani ,
We reached out to our internal team regarding the issue, and we will get back to you soon.
Thank You.
Following your concern, we have consulted with the content author regarding the equation in question. It appears that the equation is functioning as intended despite the precision concern you raised. If you need further clarification or assistance, please don't hesitate to let us know.
Thank you.