[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 15.

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: bensam1231 on April 02, 2023, 09:40:45 PM

Quote from: patrike on March 30, 2023, 08:43:35 AM

Quote from: bensam1231 on March 29, 2023, 09:18:11 AM

Aye... Thanks.

Errr... I don't think the variable change thing really solves the original problem. The problem was it would constantly trigger if conditions were met, not only once when they're first met.

So I have two different variables, and a rule that triggers turning miners off if one variable is true. Then I have another rule when both variables are false that turns things back on. However, if it's setup normally the miners will keep resetting (turning off) as long as one of the variables is true and with the 'detect change' wont be able to know the correct state that both need to be in to turn things back on.

Thanks for the feedback.

If I understand correctly, your rules looks something like this today.
Rule#1: If Var1=true or Var2=true -> Stop miners
Rule#2: If Var1=false and Var2=false -> Start miners

Do you think this concept could work?
Rule#1: If Var1=true or Var2=true -> Set Var3=true
Rule#2: If Var1=false and Var2=false -> Set Var3=false
Rule#3: If Var3=true and Var3 has changed -> Stop miners
Rule#4: If Var3=false and Var3 has changed -> Start miners

This way the actions for Rule#3 and #4 should only run once.

This does work, I feel as though the 'detect change' or 'comparison' should instead be checkboxes, instead of radial buttons and could eliminate this, while being more intuitive and simplistic. So it could do both in one or either/or.

I don't know if you can do anything about the rulespam, but the comparison activates every 6s and keeps hitting the logs, which buries anything of value.

Thanks for the feedback.

Is it entries in the Awesome Miner log file you are referring to? I did find a few related to triggers but not many. Can you give an example and I will look into it in more detail? Thanks!

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: narousberg on March 30, 2023, 05:08:15 PM

Hi Patrike, noncerpro miner have rebranding, now this miner is onezerominer. Supports DynexSolve algo.
Please integrate in Awesome Miner this miner. Hashrate is much better with this miner.
https://github.com/OneZeroMiner/onezerominer
Regards

Thanks for the request - this one will be supported in the near future.

narousberg

legendary

Activity: 1754

Merit: 1007

Hi Patrike, something wired if miner in "Managed Miner" mode. If i set a "GPU Clocking Profile when starting" (for example i set core offset 210) all ok, offset will be applied. Then i stop miner, uncheck "GPU Clocking Profile when starting" checkbox (or recreating "Managed Miner" and field "GPU Clocking Profile when starting" is empty) the old value for core ofset will be showed in "GPU clocking" tab. Looks like AM not clear old values if value will not be explicit overriden in this mode. Please check. AM 9.9.3
Regards.

bensam1231

legendary

Activity: 1764

Merit: 1024

Quote from: patrike on March 30, 2023, 08:43:35 AM

Quote from: bensam1231 on March 29, 2023, 09:18:11 AM

Aye... Thanks.

Errr... I don't think the variable change thing really solves the original problem. The problem was it would constantly trigger if conditions were met, not only once when they're first met.

So I have two different variables, and a rule that triggers turning miners off if one variable is true. Then I have another rule when both variables are false that turns things back on. However, if it's setup normally the miners will keep resetting (turning off) as long as one of the variables is true and with the 'detect change' wont be able to know the correct state that both need to be in to turn things back on.

Thanks for the feedback.

If I understand correctly, your rules looks something like this today.
Rule#1: If Var1=true or Var2=true -> Stop miners
Rule#2: If Var1=false and Var2=false -> Start miners

Do you think this concept could work?
Rule#1: If Var1=true or Var2=true -> Set Var3=true
Rule#2: If Var1=false and Var2=false -> Set Var3=false
Rule#3: If Var3=true and Var3 has changed -> Stop miners
Rule#4: If Var3=false and Var3 has changed -> Start miners

This way the actions for Rule#3 and #4 should only run once.

This does work, I feel as though the 'detect change' or 'comparison' should instead be checkboxes, instead of radial buttons and could eliminate this, while being more intuitive and simplistic. So it could do both in one or either/or.

I don't know if you can do anything about the rulespam, but the comparison activates every 6s and keeps hitting the logs, which buries anything of value.

joseph32

member

Activity: 418

Merit: 21

Hi Patrik,

I just tested the newest AM version. Your correction to the Rigel miner API seems to be working well now. No crazy things anymore with admin rights or without or mixed on all my rigs. AM also shows the devices correctly now without setting the device order manually.

A huge thanks too you! Grin

EDIT: Yes please, integrate the OneZeroMiner. It also comes with an API. Thanks!

narousberg

legendary

Activity: 1754

Merit: 1007

Hi Patrike, noncerpro miner have rebranding, now this miner is onezerominer. Supports DynexSolve algo.
Please integrate in Awesome Miner this miner. Hashrate is much better with this miner.
https://github.com/OneZeroMiner/onezerominer
Regards

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: joseph32 on March 29, 2023, 03:36:00 PM

Hi Patrik,

or anyone who knows this Huh

And sorry if this was answered already somewhere, couldn't find it...

Just playing around with the good old Profit Profiles and the Profit Switcher. How does AM knows the second coin to calculate the profit in the Profit Switcher if I can only set the hashrates and wattages? Just as an example: I want to use Gminer to dual mine ERGO (Autolykos 2) and KASPA together, but also solo mine just KASPA, whatever combination is just the highest. The Profit Switcher only shows me the profit of ERGO and the profit of KASPA, but not the profit of ERGO+KASPA. Sorry, but I don't get it... Is this possible with the profit switcher right now? Or do I have to use the Managed Miner and switch it by hand with my profiles?

What you point out here is simply a limitation in the profit switching design right now. It was initially for the days where Ethereum was the primary coin and in addition to this could could set a dual hashrate/power for a few secondary coins. Today some software like SrbMiner-Multi can do dual mining of almost any combination of coins - so in theory you could have something like 1000 combinations.

The idea is to improve the profit switcher to handle scenarios where the primary coin is something else than EtHash.

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: bensam1231 on March 29, 2023, 09:18:11 AM

Aye... Thanks.

Errr... I don't think the variable change thing really solves the original problem. The problem was it would constantly trigger if conditions were met, not only once when they're first met.

So I have two different variables, and a rule that triggers turning miners off if one variable is true. Then I have another rule when both variables are false that turns things back on. However, if it's setup normally the miners will keep resetting (turning off) as long as one of the variables is true and with the 'detect change' wont be able to know the correct state that both need to be in to turn things back on.

Thanks for the feedback.

If I understand correctly, your rules looks something like this today.
Rule#1: If Var1=true or Var2=true -> Stop miners
Rule#2: If Var1=false and Var2=false -> Start miners

Do you think this concept could work?
Rule#1: If Var1=true or Var2=true -> Set Var3=true
Rule#2: If Var1=false and Var2=false -> Set Var3=false
Rule#3: If Var3=true and Var3 has changed -> Stop miners
Rule#4: If Var3=false and Var3 has changed -> Start miners

This way the actions for Rule#3 and #4 should only run once.

joseph32

member

Activity: 418

Merit: 21

Hi Patrik,

or anyone who knows this Huh

And sorry if this was answered already somewhere, couldn't find it...

Just playing around with the good old Profit Profiles and the Profit Switcher. How does AM knows the second coin to calculate the profit in the Profit Switcher if I can only set the hashrates and wattages? Just as an example: I want to use Gminer to dual mine ERGO (Autolykos 2) and KASPA together, but also solo mine just KASPA, whatever combination is just the highest. The Profit Switcher only shows me the profit of ERGO and the profit of KASPA, but not the profit of ERGO+KASPA. Sorry, but I don't get it... Is this possible with the profit switcher right now? Or do I have to use the Managed Miner and switch it by hand with my profiles?

EDIT: Thanks for the new version and the correction to Rigel! Will test this tomorrow.

bensam1231

legendary

Activity: 1764

Merit: 1024

Aye... Thanks.

Errr... I don't think the variable change thing really solves the original problem. The problem was it would constantly trigger if conditions were met, not only once when they're first met.

So I have two different variables, and a rule that triggers turning miners off if one variable is true. Then I have another rule when both variables are false that turns things back on. However, if it's setup normally the miners will keep resetting (turning off) as long as one of the variables is true and with the 'detect change' wont be able to know the correct state that both need to be in to turn things back on.

patrike

legendary

Activity: 3556

Merit: 1095

Awesome Miner version 9.9.3

ASIC mining
- Added support for Antminer D9
- Antminer L7 pause (sleep) and resume supported
Features
- New rule action to save current miner hashrate to Profit Profile
- Check variable trigger can be configured to detect variable changes
Integrations
- Added MagicPool.co mining pool
Changes
- The total number of temperature values in the miner list has been increased from 20 to 32
- No automatic cleanup of global variables
Mining software
- BzMiner 14.1
- CpuMiner-Opt 3.22.1
- Gminer 3.31
- Lolminer 1.72
- Miniz Miner 2.0c4
- Rigel 1.3.10
- SrbMiner-Multi 2.2.3
- XmRig 6.19.1
Corrections
- Correction for recent TeamBlackMiner API changes
- Correction to Rigel miner API processing for GPUs

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: bensam1231 on March 21, 2023, 09:34:44 AM

Quote from: patrike on March 21, 2023, 05:17:34 AM

Quote from: bensam1231 on March 17, 2023, 11:12:03 PM

Quote from: patrike on March 14, 2023, 08:50:31 AM

Quote from: bensam1231 on March 12, 2023, 01:04:44 AM

Is there anyway to setup rules taking precedent over other rules, so if one is active or has been triggered, another that adjusts the same condition wont trigger?

This should be possible to solve using the variable concept. You have a trigger called "Check variable" and an action called "Set variable". The variable can either be set on a global scope or set per miner.

You can design the first rule to set a variable to "1" when running. The second rule could check the variable value and only run if the value is "0". This way you can have one rule to change the behavior of when another rule should run.

Looks like when I restart AM, some of the global variables disappear from tools > rules > variables? Do they automatically show up when rules get called that trigger them or if they aren't there will the program throw a error?

Also how do you get something to trigger once on a variable state change? Seems they're set to constantly repeat. You can set time limit, but that's not applicable nor do I want triggers to run when the variable states don't change.

Thanks

When starting Awesome Miner, all global variables not referenced by any rule will be removed. The original idea was to avoid getting a large number of unused variables but there can be scenarios where this behavior isn't preferred. I will remove the automatic cleanup of global variables in the next release.

If you would reference a variable that doesn't exist it will be considered to have a value of 0 if you read it and it will be created if you write to it.

It's true that the "Check trigger" will run every 5 seconds if the condition is true. Can you combine with "Limit actions to run at most once every" or "Limit actions per day" depending on the behavior you want? Another possibility is to make use of a second variable that you set to "1" in the rule action and you check for it to not be "1" in the trigger condition.

Isn't that just a loop or completely break the automation till it's manually reset?

I saw the run X number of minutes, but when you have a interaction that's semi-random in nature, you can't set something like that up. I think 'on state change' instead of running in a loop would be possible and often times preferable depending on what you're looking for.

I agree that there can be scenarios where a change detection is easiest. I think it will be quite fast to add to the existing Check Variable trigger so you can expect it in the near future.

bensam1231

legendary

Activity: 1764

Merit: 1024

Quote from: patrike on March 21, 2023, 05:17:34 AM

Quote from: bensam1231 on March 17, 2023, 11:12:03 PM

Quote from: patrike on March 14, 2023, 08:50:31 AM

Quote from: bensam1231 on March 12, 2023, 01:04:44 AM

Is there anyway to setup rules taking precedent over other rules, so if one is active or has been triggered, another that adjusts the same condition wont trigger?

This should be possible to solve using the variable concept. You have a trigger called "Check variable" and an action called "Set variable". The variable can either be set on a global scope or set per miner.

You can design the first rule to set a variable to "1" when running. The second rule could check the variable value and only run if the value is "0". This way you can have one rule to change the behavior of when another rule should run.

Looks like when I restart AM, some of the global variables disappear from tools > rules > variables? Do they automatically show up when rules get called that trigger them or if they aren't there will the program throw a error?

Also how do you get something to trigger once on a variable state change? Seems they're set to constantly repeat. You can set time limit, but that's not applicable nor do I want triggers to run when the variable states don't change.

Thanks

When starting Awesome Miner, all global variables not referenced by any rule will be removed. The original idea was to avoid getting a large number of unused variables but there can be scenarios where this behavior isn't preferred. I will remove the automatic cleanup of global variables in the next release.

If you would reference a variable that doesn't exist it will be considered to have a value of 0 if you read it and it will be created if you write to it.

It's true that the "Check trigger" will run every 5 seconds if the condition is true. Can you combine with "Limit actions to run at most once every" or "Limit actions per day" depending on the behavior you want? Another possibility is to make use of a second variable that you set to "1" in the rule action and you check for it to not be "1" in the trigger condition.

Isn't that just a loop or completely break the automation till it's manually reset?

I saw the run X number of minutes, but when you have a interaction that's semi-random in nature, you can't set something like that up. I think 'on state change' instead of running in a loop would be possible and often times preferable depending on what you're looking for.

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: sxemini on March 21, 2023, 06:55:07 AM

Hi patrike,

I did some more tests.
Teamredminer dual mining is not working like it should. Awesomeminer doesn´t add the part for the second coin, i must add the whole commandline by myself. Hashrates is shown correctly.

The other thing is a little bit strange, but i will do some further tests.
Kaspa+Zil is working as it should on 1 rig - AM show me the kaspa pool and hashrate, but on an other rig AM only show me the zil pool with the kaspa hashrate. Commandline is identical Cheesy

Thanks for the feedback.

For mining with TeamRedMiner, only a few algorithm combinations are enabled for dual based on the documentation for TRM. What are the algorithm combination you are trying here? Could you please send me the command line you use to manually launch TRM dual mining and I will try the same with Awesome Miner. You can send the command line to me via PM. Thanks!

Quote from: sxemini on March 21, 2023, 06:55:07 AM

The other thing is a little bit strange, but i will do some further tests.
Kaspa+Zil is working as it should on 1 rig - AM show me the kaspa pool and hashrate, but on an other rig AM only show me the zil pool with the kaspa hashrate. Commandline is identical Cheesy

Is this also for TeamRedMiner?

sxemini

member

Activity: 1558

Merit: 69

Hi patrike,

I did some more tests.
Teamredminer dual mining is not working like it should. Awesomeminer doesn´t add the part for the second coin, i must add the whole commandline by myself. Hashrates is shown correctly.

The other thing is a little bit strange, but i will do some further tests.
Kaspa+Zil is working as it should on 1 rig - AM show me the kaspa pool and hashrate, but on an other rig AM only show me the zil pool with the kaspa hashrate. Commandline is identical Cheesy

Gminer added Dual and Triple mining Conflux (octupus) + kaspa + zil.

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: biret_06 on March 20, 2023, 05:25:45 AM

Quote from: bensam1231 on March 17, 2023, 11:12:03 PM

Quote from: patrike on March 14, 2023, 08:50:31 AM

Quote from: bensam1231 on March 12, 2023, 01:04:44 AM

Is there anyway to setup rules taking precedent over other rules, so if one is active or has been triggered, another that adjusts the same condition wont trigger?

This should be possible to solve using the variable concept. You have a trigger called "Check variable" and an action called "Set variable". The variable can either be set on a global scope or set per miner.

You can design the first rule to set a variable to "1" when running. The second rule could check the variable value and only run if the value is "0". This way you can have one rule to change the behavior of when another rule should run.

Looks like when I restart AM, some of the global variables disappear from tools > rules > variables? Do they automatically show up when rules get called that trigger them or if they aren't there will the program throw a error?

Also how do you get something to trigger once on a variable state change? Seems they're set to constantly repeat. You can set time limit, but that's not applicable nor do I want triggers to run when the variable states don't change.

Thanks

1)can I pay with cryptocurrency for the full version?
2)For residents of the Russian Federation, are there sanctions from awesome miner?

I've responded to the message you sent via the contact form on our web site.

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: bensam1231 on March 17, 2023, 11:12:03 PM

Quote from: patrike on March 14, 2023, 08:50:31 AM

Quote from: bensam1231 on March 12, 2023, 01:04:44 AM

Is there anyway to setup rules taking precedent over other rules, so if one is active or has been triggered, another that adjusts the same condition wont trigger?

This should be possible to solve using the variable concept. You have a trigger called "Check variable" and an action called "Set variable". The variable can either be set on a global scope or set per miner.

You can design the first rule to set a variable to "1" when running. The second rule could check the variable value and only run if the value is "0". This way you can have one rule to change the behavior of when another rule should run.

Looks like when I restart AM, some of the global variables disappear from tools > rules > variables? Do they automatically show up when rules get called that trigger them or if they aren't there will the program throw a error?

Also how do you get something to trigger once on a variable state change? Seems they're set to constantly repeat. You can set time limit, but that's not applicable nor do I want triggers to run when the variable states don't change.

Thanks

When starting Awesome Miner, all global variables not referenced by any rule will be removed. The original idea was to avoid getting a large number of unused variables but there can be scenarios where this behavior isn't preferred. I will remove the automatic cleanup of global variables in the next release.

If you would reference a variable that doesn't exist it will be considered to have a value of 0 if you read it and it will be created if you write to it.

It's true that the "Check trigger" will run every 5 seconds if the condition is true. Can you combine with "Limit actions to run at most once every" or "Limit actions per day" depending on the behavior you want? Another possibility is to make use of a second variable that you set to "1" in the rule action and you check for it to not be "1" in the trigger condition.

biret_06

newbie

Activity: 2

Merit: 0

Quote from: bensam1231 on March 17, 2023, 11:12:03 PM

Quote from: patrike on March 14, 2023, 08:50:31 AM

Quote from: bensam1231 on March 12, 2023, 01:04:44 AM

Is there anyway to setup rules taking precedent over other rules, so if one is active or has been triggered, another that adjusts the same condition wont trigger?

This should be possible to solve using the variable concept. You have a trigger called "Check variable" and an action called "Set variable". The variable can either be set on a global scope or set per miner.

You can design the first rule to set a variable to "1" when running. The second rule could check the variable value and only run if the value is "0". This way you can have one rule to change the behavior of when another rule should run.

Looks like when I restart AM, some of the global variables disappear from tools > rules > variables? Do they automatically show up when rules get called that trigger them or if they aren't there will the program throw a error?

Also how do you get something to trigger once on a variable state change? Seems they're set to constantly repeat. You can set time limit, but that's not applicable nor do I want triggers to run when the variable states don't change.

Thanks

1)can I pay with cryptocurrency for the full version?
2)For residents of the Russian Federation, are there sanctions from awesome miner?

bensam1231

legendary

Activity: 1764

Merit: 1024

Quote from: patrike on March 14, 2023, 08:50:31 AM

Quote from: bensam1231 on March 12, 2023, 01:04:44 AM

Is there anyway to setup rules taking precedent over other rules, so if one is active or has been triggered, another that adjusts the same condition wont trigger?

This should be possible to solve using the variable concept. You have a trigger called "Check variable" and an action called "Set variable". The variable can either be set on a global scope or set per miner.

You can design the first rule to set a variable to "1" when running. The second rule could check the variable value and only run if the value is "0". This way you can have one rule to change the behavior of when another rule should run.

Looks like when I restart AM, some of the global variables disappear from tools > rules > variables? Do they automatically show up when rules get called that trigger them or if they aren't there will the program throw a error?

Also how do you get something to trigger once on a variable state change? Seems they're set to constantly repeat. You can set time limit, but that's not applicable nor do I want triggers to run when the variable states don't change.

Thanks

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: bensam1231 on March 12, 2023, 01:04:44 AM

Is there anyway to setup rules taking precedent over other rules, so if one is active or has been triggered, another that adjusts the same condition wont trigger?

This should be possible to solve using the variable concept. You have a trigger called "Check variable" and an action called "Set variable". The variable can either be set on a global scope or set per miner.

You can design the first rule to set a variable to "1" when running. The second rule could check the variable value and only run if the value is "0". This way you can have one rule to change the behavior of when another rule should run.

Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 15. (Read 703766 times)