Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

each ∎ represents a count of 1 #1

Open
aroberts394 opened this issue Dec 27, 2019 · 4 comments
Open

each ∎ represents a count of 1 #1

aroberts394 opened this issue Dec 27, 2019 · 4 comments

Comments

@aroberts394
Copy link

Phenomenal job on this! I was looking all over for something like this? Do you know we can implement this on our cluster? Thank you so much for adding this on github!

Also, does each ∎ represent each job within the array?

@aroberts394
Copy link
Author

Also for some reason, the elapsed time count doesn't add up with the number of jobs within the array. Is this correct?

image

@tlangfor
Copy link
Contributor

tlangfor commented Jan 2, 2020

Hi @aroberts394, thanks for checking seff-array out!

The scaling of the histograms is dynamic, so for larger arrays each box can represent more than one job. In the example you posted above, the array size is small enough so the boxes are for a count of 1.

As for the elapsed time information, that does look odd. Could you post the output from this slurm command:

sacct -p -j 97828 --format=JobID,JobName,MaxRSS,Elapsed,ReqMem,ReqCPUS,Timelimit

This is the information that seff-array parses to make the histograms, so there might be something funny going on with the text parsing.

Cheers,
-t

@aroberts394
Copy link
Author

Thanks for the reply. That's really interesting and I think scaling dynamically is a good feature.
Below is what the output looks like:
image
image
image
image

@hl723
Copy link
Collaborator

hl723 commented May 27, 2020

Hello @aroberts394,

I am a new intern working on seff-array. So far, I fixed some bugs (including dynamic scaling of histograms) and added some enhancements to seff-array. I hope you can check this new version out! If the issue still exists, I would be glad to look into it!

-Hao

@hl723 hl723 closed this as completed May 27, 2020
@hl723 hl723 reopened this May 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants