[NemosMiner] multi algo profit switching NVIDIA/CPU miner - page 3.

InfiniteImp

newbie

Activity: 33

Merit: 0

Quote from: MrPlus on December 04, 2018, 03:29:32 AM

You can copy your stats folder over. Files are compatible. This will avoid benchmark Wink

Thanks, I'll do that on the other PC when I move from Nemos. Yesterday I updated one machine. So far, interestingly enough, neither machine has crashed since yesterday. I did disable the "monitoring" feature on Nemos. I wonder if that may have been a contributing factor.
EDIT: Nemos just crashed with a NULL error executing a $TimerUI event (I think). NPlus still running error-free.

STEVLTH

newbie

Activity: 24

Merit: 0

Quote from: MrPlus on December 04, 2018, 07:24:32 AM

NPlusMiner has that corrected
https://github.com/MrPlusGH/NPlusMiner

I pushed a pull request on GitHub to correct ZPool. should be ok in the last version of NemosMiner
I pushed pull requests on GitHub to fix PhiPhiPool. Should be ok in the Next version of NemosMiner

If you want it fixed right now. You could get NPlusMiner and copy your stats and config folders over to keep your config and avoid re-benchmark.

+MrPlus

And again, thanks a lot! I'll try NPlusMiner.

MrPlus

member

Activity: 514

Merit: 11

Quote from: STEVLTH on December 01, 2018, 07:22:00 AM

Hi, minerx117

Thanks for NM updates. v3.5.5 works fine for me. But I found some issues:

1. Pools/Zpool.ps1 missing one `}` at the end of the code.
2. PhiPhiPool doesn't show balance and doesn't generate phiphipoolplus.json for a BrainPlus mode.

Also one question about BrainPlus. If I replace $PriceField = "actual_last24h" with $PriceField = "estimate_current" (and reduce SampleSizeMinutes and TrendSpanSizeMinutes) will it work correctly if I want to interpolate current profit just a little bit to avoid frequent spikes of network difficulty in some algorithms? Thanks!

NPlusMiner has that corrected
https://github.com/MrPlusGH/NPlusMiner

I pushed a pull request on GitHub to correct ZPool. should be ok in the last version of NemosMiner
I pushed pull requests on GitHub to fix PhiPhiPool. Should be ok in the Next version of NemosMiner

If you want it fixed right now. You could get NPlusMiner and copy your stats and config folders over to keep your config and avoid re-benchmark.

+MrPlus

MrPlus

member

Activity: 514

Merit: 11

Quote from: InfiniteImp on December 03, 2018, 08:29:01 PM

Quote from: MrPlus on December 03, 2018, 01:50:19 PM

@ People with UI Exceptions.

Could you give a quick try to NPlusMiner to see if you get the same issue.

Nemo and I work together and share the code.
It would help debug.

Thanks,
+MrPlus
https://github.com/MrPlusGH/NPlusMiner

Will do. Means I'll need to re-benchmark everything but well worth it if it means helping fix these crashes!

You can copy your stats folder over. Files are compatible. This will avoid benchmark Wink

STEVLTH

newbie

Activity: 24

Merit: 0

Quote from: MrPlus on December 03, 2018, 01:48:09 PM

Plus already does avoid price spikes but you can play with config in the XML to change the the SampleSizeMinutes. TrendSpanSizeMinutes is not used yet.

Do not change $PriceField. Plus works by making sense of estimate_current based on actual_last24.

60
Duration of the dataset used for analisys (Minutes)
30
Not used
0
If you want more recent data to have more impact than older data. This coefficient will be applied to data of SampleSizeMinutes /2
1
Simple price multiplicator
60
Pool API poll interval (Seconds)
false
Self explanatory

+MrPlus
Try NPLusMiner with new charts for Earnings Tracker
https://github.com/MrPlusGH/NPlusMiner

Thanks a lot!

InfiniteImp

newbie

Activity: 33

Merit: 0

By the way, I got errors today which seem to indicate more like an environment corruption. Never mind just a NULL object slipping through - it loses access to (what I presume are) built-in functions like "write-host" and IsLoaded

Error 1:

Write-Host : The term 'Write-Host' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\NemosMiner\NemosMiner.ps1:337 char:25
+ Write-Host "Running:"
+ ~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Write-Host:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

You cannot call a method on a null-valued expression.
At C:\NemosMiner\NemosMiner.ps1:381 char:13
+ $TimerUI.Start()
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (

[], RuntimeException
+ FullyQualifiedErrorId : InvokeMethodOnNull

Error 2:

IsLoaded : The term 'IsLoaded' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\NemosMiner\NemosMiner.ps1:1519 char:19
+ if (!(IsLoaded(".\Core.ps1"))) {. .\Core.ps1; RegisterLoa ...
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (IsLoaded:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

InfiniteImp

newbie

Activity: 33

Merit: 0

Quote from: MrPlus on December 03, 2018, 01:50:19 PM

@ People with UI Exceptions.

Could you give a quick try to NPlusMiner to see if you get the same issue.

Nemo and I work together and share the code.
It would help debug.

Thanks,
+MrPlus
https://github.com/MrPlusGH/NPlusMiner

Will do. Means I'll need to re-benchmark everything but well worth it if it means helping fix these crashes!

MrPlus

member

Activity: 514

Merit: 11

@ People with UI Exceptions.

Could you give a quick try to NPlusMiner to see if you get the same issue.

Nemo and I work together and share the code.
It would help debug.

Thanks,
+MrPlus
https://github.com/MrPlusGH/NPlusMiner

MrPlus

member

Activity: 514

Merit: 11

Quote from: STEVLTH on December 01, 2018, 07:22:00 AM

Hi, minerx117

Thanks for NM updates. v3.5.5 works fine for me. But I found some issues:

1. Pools/Zpool.ps1 missing one `}` at the end of the code.
2. PhiPhiPool doesn't show balance and doesn't generate phiphipoolplus.json for a BrainPlus mode.

Also one question about BrainPlus. If I replace $PriceField = "actual_last24h" with $PriceField = "estimate_current" (and reduce SampleSizeMinutes and TrendSpanSizeMinutes) will it work correctly if I want to interpolate current profit just a little bit to avoid frequent spikes of network difficulty in some algorithms? Thanks!

Plus already does avoid price spikes but you can play with config in the XML to change the the SampleSizeMinutes. TrendSpanSizeMinutes is not used yet.

Do not change $PriceField. Plus works by making sense of estimate_current based on actual_last24.

60
Duration of the dataset used for analisys (Minutes)
30
Not used
0
If you want more recent data to have more impact than older data. This coefficient will be applied to data of SampleSizeMinutes /2
1
Simple price multiplicator
60
Pool API poll interval (Seconds)
false
Self explanatory

+MrPlus
Try NPLusMiner with new charts for Earnings Tracker
https://github.com/MrPlusGH/NPlusMiner

Inves

member

Activity: 168

Merit: 10

How to configure on ubuntu?

STEVLTH

newbie

Activity: 24

Merit: 0

Hi, minerx117

Thanks for NM updates. v3.5.5 works fine for me. But I found some issues:

1. Pools/Zpool.ps1 missing one `}` at the end of the code.
2. PhiPhiPool doesn't show balance and doesn't generate phiphipoolplus.json for a BrainPlus mode.

Also one question about BrainPlus. If I replace $PriceField = "actual_last24h" with $PriceField = "estimate_current" (and reduce SampleSizeMinutes and TrendSpanSizeMinutes) will it work correctly if I want to interpolate current profit just a little bit to avoid frequent spikes of network difficulty in some algorithms? Thanks!

nospampls

newbie

Activity: 18

Merit: 0

Well according to my .log, it's occurring between the Comparing miners and pools.. and Launching Prerun: stage during a cycle. Since those status strings show up in Core.ps1, maybe the problem lies within there?

Code:

Starting Cycle
Loading BTC rate from 'api.coinbase.com'..
Loading pool stats..
Computing pool stats..
Loading miners..
Comparing miners and pools..
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression."
closing current miner and switching
Launching Prerun: .\Prerun\default.bat
Starting miner

I also noticed this error occuring in the CoreCycle.log: This error repeats quite a few times in the log.

Code:

+ CategoryInfo : NotSpecified: (:) [], SetValueInvocationException
   + FullyQualifiedErrorId : ScriptSetValueRuntimeException
Exception setting "StatusText": "The 'Add-Member' command was found in the module 'Microsoft.PowerShell.Utility', but
the module could not be loaded. For more information, run 'Import-Module Microsoft.PowerShell.Utility'."
At D:\Mining\NemosMiner-v3.5.1\Core.ps1:171 char:4
+ $Variables.StatusText = "! Error contacting pool retrying ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   + CategoryInfo : NotSpecified: (:) [], SetValueInvocationException
   + FullyQualifiedErrorId : ScriptSetValueRuntimeException

Since you think it may be pool-based, maybe it errors out when the pool cant be reached for a moment?
I'm using standard zpool. Nemo says he uses Nicehash and Zpool24hr: https://bitcointalksearch.org/topic/m.47377248

Just throwing out some information to hopefully help you or whoever solve the issues!

InfiniteImp

newbie

Activity: 33

Merit: 0

The annoying thing is that I don't know where the error is happening. The first one was easier to track down as it referenced 'out-file'. That only happens in a few places. The null error could be in a lot of places. So far no luck.

I wonder if this is pool-based. Maybe the reason Nemo doesn't get it is the particular pool or combination of pools he uses doesn't hit that error.

nospampls

newbie

Activity: 18

Merit: 0

Quote from: InfiniteImp on November 30, 2018, 12:55:17 AM

Looks like release 3.5.5 broke it for me. I just got a crash but in another place and a different error (not the one I patched). This time it's a "You cannot call a method on a null-valued expression".

I'll dig into it.

I had that one a while back: https://bitcointalksearch.org/topic/m.46856313
Increasing the interval (mines at 900 / 15 mins) pretty much stopped that crash for me, but it the error still exists.

I don't understand code well enough to solve this one myself, but if you check the Logs\miner.log you can see repeated PS>TerminatingError(ForEach-Object): "You cannot call a method on a null-valued expression." errors on every cycle.

And in terms of updating, I've been running Nemo's for over a year now. Version 3.0 was the most stable release for me so I used it until it became too outdated to keep updated when the GUI changed. The way I do it now, since Nemo's is a pretty modular package, is I update selective parts from github that I feel are necessary or are significant improvements instead of moving to a fresh release every time. This has let me keep my rigs up longer and troubleshoot much less! Cheesy

Edit: And look what I just got... https://i.imgur.com/FuVfRWU.jpg

InfiniteImp

newbie

Activity: 33

Merit: 0

Quote from: nospampls on November 30, 2018, 12:27:31 AM

Quote from: InfiniteImp on November 29, 2018, 10:38:24 PM

Don't forget to close down and restart the miner!

Of course! Had everything closed while I made the edit. It has ran all day without a hitch since.
Still too soon to called it fixed as I've had many days without crashes before making the edit, but it looks promising so far. Thanks again!

Looks like release 3.5.5 broke it for me. I just got a crash but in another place and a different error (not the one I patched). This time it's a "You cannot call a method on a null-valued expression".

I'll dig into it.

nospampls

newbie

Activity: 18

Merit: 0

Quote from: InfiniteImp on November 29, 2018, 10:38:24 PM

Don't forget to close down and restart the miner!

Of course! Had everything closed while I made the edit. It has ran all day without a hitch since.
Still too soon to called it fixed as I've had many days without crashes before making the edit, but it looks promising so far. Thanks again!

InfiniteImp

newbie

Activity: 33

Merit: 0

Quote from: nospampls on November 29, 2018, 12:39:29 PM

^ @InfiniteImp

Thanks for sharing! I'm giving it a test on one of my rigs right now. Let's hope it does the trick!

Don't forget to close down and restart the miner!

nospampls

newbie

Activity: 18

Merit: 0

^ @InfiniteImp

Thanks for sharing! I'm giving it a test on one of my rigs right now. Let's hope it does the trick!

InfiniteImp

newbie

Activity: 33

Merit: 0

Ok @nospampls and @Khazore I have a fix for you.

It may not be the ideal fix as I've never worked with PowerShell before but it addresses the .NET crashes. I've been running for almost 24 hours and by now I would have had at least 1 crash on each machine so I'm considering this addressed.

I'm making a bunch of assumptions here as to how PowerShell works. While I do program, I've never worked in this environment so take the notes below as my best guess as to what's happening.

Open the file "NemosMiner.ps1" (notepad should be fine)

The issue is with this line:

$PSItem.ToString() | out-file .\logs\excepUI.txt -Append

It's meant to log errors to the exceptUI.txt error log but sometimes it ends up on this line with a NULL $PSItem object. Powershell isn't happy about doing a .ToString on a null object and errors out. However since it's already on this line because of a different error (likely the fact that the object is NULL

) it just crashes out as an unptrapped error.

So, simple fix: Add a # in front of $PSItem. That turns the line into a comment. You lose the logging of UI errors but I'll take that over an untrapped crash any day! The new line should look like this:

# $PSItem.ToString() | out-file .\logs\excepUI.txt -Append

Enjoy!

achmadsutanto

copper member

Activity: 221

Merit: 0

Hi,
I am searching Linux YescyptR32 miner for GPU (nVidia or AMD), is it available on nemosminer?

Topic: [NemosMiner] multi algo profit switching NVIDIA/CPU miner - page 3. (Read 289447 times)