Noticed when running the stampede data, the code exited with the following error in the timeConversion(raw) function:
ValueError: invalid literal for int() with base 10: 'Partition_Limit'
Error occurred for file: 2015-08-23.txt
The "Timelimit" column of the dataset was set for one line to "Partition_Limit", which should have been a valid "numerical" time instance. Dug into the stampede user guide and the longest amount of time a job can be submitted for is 2 days, suggesting to create a if statement that would check to see if the "Partition_Limit" was found and if so, set the max_minutes to 2 days.
Partition_Limit, according to SLURM, is on a case-by-case basis for each instantiation of the SLURM scheduler, so it's up to each HPC system what that max timelimit is.
Noticed when running the stampede data, the code exited with the following error in the timeConversion(raw) function:
ValueError: invalid literal for int() with base 10: 'Partition_Limit'
Error occurred for file: 2015-08-23.txt
The "Timelimit" column of the dataset was set for one line to "Partition_Limit", which should have been a valid "numerical" time instance. Dug into the stampede user guide and the longest amount of time a job can be submitted for is 2 days, suggesting to create a if statement that would check to see if the "Partition_Limit" was found and if so, set the max_minutes to 2 days.
Partition_Limit, according to SLURM, is on a case-by-case basis for each instantiation of the SLURM scheduler, so it's up to each HPC system what that max timelimit is.