salfter's switchers custom fan management conflicting with tempcontrol fan settings about nvoc_by_fullzero_community_release HOT 17 CLOSED

Removed "Blake-Vanilla" and changed "Cryptonight" to "Cryptonight-Monero", still same error.

from nvoc_by_fullzero_community_release.

from nvoc_by_fullzero_community_release.

Your eagle eyes ...
Fixed it in 3main, also needed to change the output_dir to :

But temp control giving error, no problem on manual coin

GPU 0, Sat May 12 13:37:10 +0430 2018 - Adjusting fan from: 30 to: 50 Temp: 58


ERROR: Error assigning value 50 to attribute 'GPUTargetFanSpeed'
       (m1-desktop-100:0[fan:0]) as specified in assignment
       '[fan:0]/GPUTargetFanSpeed=50' (Unknown Error).

GPU 1, Target temp: 65, Current: 48, Diff: 17, Fan: 53, Power: 78.10

GPU 1, Sat May 12 13:37:11 +0430 2018 - Adjusting fan from: 53 to: 50 Temp: 48


ERROR: Error assigning value 50 to attribute 'GPUTargetFanSpeed'
       (m1-desktop-100:0[fan:1]) as specified in assignment
       '[fan:1]/GPUTargetFanSpeed=50' (Unknown Error).

GPU 2, Target temp: 65, Current: 51, Diff: 14, Fan: 64, Power: 77.79

GPU 2, Sat May 12 13:37:11 +0430 2018 - Adjusting fan from: 64 to: 59 Temp: 51


ERROR: Error assigning value 59 to attribute 'GPUTargetFanSpeed'
       (m1-desktop-100:0[fan:2]) as specified in assignment
       '[fan:2]/GPUTargetFanSpeed=59' (Unknown Error).

from nvoc_by_fullzero_community_release.

Add that missing slashes directly into every python script instead of 3main, such that it's more robust since the standard way of specifying paths is without the ending slash, eventually, a double slash would occur it will also work fine.

from nvoc_by_fullzero_community_release.

When you say the tempcontrol is fine in manual coin, does it also mean that is fine with WTM switcher?

from nvoc_by_fullzero_community_release.

Like this?
log=open(outputDir + "/" + "current-profit", "w")
or this:
log=open(outputDir/ + "current-profit", "w")

And yes, tested WTM and its working fine with it too.

from nvoc_by_fullzero_community_release.

log=open(outputDir + "/current-profit", "w")

from nvoc_by_fullzero_community_release.

Ok, I'm trying to figure out why mph and other salfter's switchers are doing things in a certain manner. Will do some changes later today. meanwhile go ahead with #57

from nvoc_by_fullzero_community_release.

Looks like there is a fan setting at the end of mph_switch and it conflict with tempcontrol

from nvoc_by_fullzero_community_release.

Yeah, but the point here is to understand why the switcher was taking care of managing OC and fans by itself given it's not implemented as a standalone parallel job. All the things I see should make sense only if its developer originally intended to switch the mining algo in a transparent way without the need to loop directly into 3main. Moreover, why the json is created only if auto_start_miner = YES an the guake tab is created twice in LOCAL mode?

from nvoc_by_fullzero_community_release.

I never used safter switchers so never checked/edited them, was just checking it for 2.1 and got the temp error.
We can move if auto_start_miner == yes to after creating json, but no idea why it creates 2 guake tabs.
In 3main I see 2 guake commands, one has "-n 1" arg to create new tab, other one dont.
And I was testing it from remote ssh, but my test rig setting is LOCAL.
Will test more when I get home beside my test rig.

from nvoc_by_fullzero_community_release.

"Manual_fan == yes && tempcontrol == no ", does not set fan speed too when using salfter switcher

from nvoc_by_fullzero_community_release.

Removed the last fan part and all is good for now

from nvoc_by_fullzero_community_release.

That one in the python switcher code?

from nvoc_by_fullzero_community_release.

Ok, that kind of incompatibilities were expected to emerge since the old 3main control flow was a complete mess. Now, the correct (but annoying) way of fixing this incompatibility should be to manage the manual fan control as like as OC & PL, but I think removing fan management from those switchers could be ok since you're not interested into ALGO_SPECIFIC manual fan policies

from nvoc_by_fullzero_community_release.

Yes, now I see that programmatic has those disabled too

from nvoc_by_fullzero_community_release.

Fixed into #59

from nvoc_by_fullzero_community_release.