Skip to content

Conversation

@dmiskovic-NV
Copy link
Contributor

As discussed in #280

@github-actions
Copy link

github-actions bot commented Jan 24, 2023

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

Copy link
Contributor

@arjunsuresh arjunsuresh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @dmiskovic-NV for the fix. LGTM

@dmiskovic-NV dmiskovic-NV changed the title hopeful fix for dirty PSUs hopeful fix for dirty PSUs [DONOTUSE-WIP] Jan 25, 2023
@dmiskovic-NV
Copy link
Contributor Author

marked as DONOTUSE, since there is some error in logic. will fix it tomorrow.

# in case such things are not done, peaks over 3x range will be cut off, so measured/reported power will be reported as lower than realistic

if self._maxAmps is not None and self._maxVolts is not None:
w = float(self._maxAmps) * float(self._maxVolts)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here power factor must also be multiplied right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

exactly. and to get that, i need to modify max_volts_amps which will break all unit tests and when doing that, i'll just either base decision on power factor alone or rather on real power

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh sure. I think using power factor alone should be reasonable here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we'd need to make number up since power factor is not 100% reliable indicator of peak. THD is better, but PTD doesn't gather that. so instead i opted for modifying the function and also grabbing power

@dmiskovic-NV
Copy link
Contributor Author

Ready for review and testing

@dmiskovic-NV dmiskovic-NV changed the title hopeful fix for dirty PSUs [DONOTUSE-WIP] hopeful fix for dirty PSUs [ready for review and testing] Jan 26, 2023
@nv-ananjappa
Copy link

@nv-etcheng Could you review?

Copy link
Contributor

@araghun araghun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved per alignment in 1/31 PowerWG

@s-idgunji s-idgunji merged commit 521f9ce into mlcommons:master Feb 3, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Feb 3, 2023
@s-idgunji
Copy link
Contributor

Merging per the discussion in Power WG meeting ( Jan 31 2023) . A vote was taken to approve this PR

@dmiskovic-NV dmiskovic-NV deleted the dejan-nv-dirty-psu-fix branch February 3, 2023 17:49
@s-idgunji
Copy link
Contributor

@dmiskovic-NV , @araghun , @arjunsuresh - We need to remove this from master and can reintroduce it when new PTD comes through since this is patch work. We now have submission checker to check ranging/testing and we should not add any CF or range changes manually. Let's get all the tuning be done through PTD in ranging for 3.1

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants