Closed Sunt-ing closed 1 month ago
The workaround looks good as it directly addresses the what the warning is saying, but I kinda feel weird because the CSV file (in theory) should not contain any NA values. I also believe empty dataframes are also avoided by catching pd.errors.EmptyDataError
. Could you print out the two dataframes inside _update_df
?
Sure!
power_df
time power0
0 1.715177e+09 67.876
1 1.715177e+09 68.867
2 1.715177e+09 68.149
3 1.715177e+09 67.677
4 1.715177e+09 68.832
... ... ...
1047 1.715177e+09 24.929
1048 1.715177e+09 24.945
1049 1.715177e+09 24.929
1050 1.715177e+09 24.945
1051 1.715177e+09 24.945
[1052 rows x 2 columns]
additional_df
time power0
0 1.715177e+09 24.929
1 1.715177e+09 24.945
2 1.715177e+09 24.945
3 1.715177e+09 24.945
4 1.715177e+09 24.945
.. ... ...
995 1.715177e+09 24.945
996 1.715177e+09 24.945
997 1.715177e+09 24.945
998 1.715177e+09 24.929
999 1.715177e+09 24.945
[1000 rows x 2 columns]
Fixed. Let me know if this still happens!
Describe the bug Not a real bug but an improvement from my perspective.
When using PowerMonitor on Cloudlab c240g5 P100 GPU, the warnings are really annoying and interfere my reading CLI outputs.
To Reproduce
Outputs are like:
My workaround is something like this:
But you may propose better solutions.
I also suggest adding an example of PowerMonitor since it has some docs already and can be useful to developers.