Corner case issue
We discussed this issue at 3rd BREAKOUT MEETING (05.20.).
We have to consider the case where CPU resources are not allocated to any process. The first uploaded Jupyter notebook file does not reflect the corresponding corner case.
The unfortunate thing is that the first uploaded code seems to have to reflect the corener case syntactically. However, in reality, it was a code that did not output the desired result. The reason is currently under analysis.
Although the cause was not clearly identified, it was corrected by finding a case where CPU resources were not allocated to any process and overwriting it with a white box. We can see this in action in the image below.
The above example is the result of forcibly changing data so that a corner case occurs in the tc1 testcase.
result_FCFS.loc[0,'S'] = 1
result_FCFS.loc[2,'S'] = 7
result_PPRIORITY.loc[7,'S'] = 21
result_RR.loc[4,'S'] = 8
result_FCFS
Note : Check that the above result follows the fact that the logic for handling edge cases in the image and animation generation code is different, but the result should be the same.
Note : It should be noted that the overwrite algorithm is written differently in simple image creation and animation creation.
'학부공부 > OS_운영체제' 카테고리의 다른 글
TP1.8. Animation Ideas [OS Scheduling simulator] (0) | 2022.06.06 |
---|---|
TP1.7. History in Colab shared links [OS Scheduling simulator] (2) | 2022.06.06 |
TP1.5. File format for Evaluation module [OS Scheduling simulator] (2) | 2022.06.06 |
TP1.4. Python : GanttChart [OS Scheduling simulator] (0) | 2022.06.06 |
TP1.3. 05.20. BREAKOUT MEETING [OS Scheduling simulator] (2) | 2022.06.06 |
댓글