Agreed, just trying to apply the principle of kindness to their arguments.
Agreed, just trying to apply the principle of kindness to their arguments. What I want for a battery indicator is more a dual battery indicator/workload indicator. Aka, lets say some process goes nuts for 10 seconds, I'd want some sort of "hey this thing started up over here and is using energy like a fiend" alert. But if I were on power then I'd say only do that after 30 seconds or whatever. That and also keep historic power use and tie that into current use and times and it would seem like you could have some really stupid ML/linear regression to figure out: the user normally runs a compile every 4pm, and its 4pm and he's not on power so that means it'll likely use XMah which means based on the power available he's got about... N minutes of power remaining. Still seems a stupidly annoying problem to solve with so many variables.
Posted by mitchty on Dec 16, 2016, 4:31 PM
Tags
Related issues
- The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
- The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
- (My comment is about detached houses).
- The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
- > steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
- Why is there no comparison with FLUX 3 Image?
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
hackernews (Other)
The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
NewThe biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
(My comment is about detached houses).
The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
> steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
Why is there no comparison with FLUX 3 Image?
> our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...
Why is there no contact form?
Agreed, just trying to apply the principle of kindness to their arguments.
Agreed, just trying to apply the principle of kindness to their arguments. What I want for a battery indicator is more a dual battery indicator/workload indicator. Aka, lets say some process goes nuts for 10 seconds, I'd want some sort of "hey this thing started up over here and is using energy like a fiend" alert. But if I were on power then I'd say only do that after 30 seconds or whatever. That and also keep historic power use and tie that into current use and times and it would seem like you could have some really stupid ML/linear regression to figure out: the user normally runs a compile every 4pm, and its 4pm and he's not on power so that means it'll likely use XMah which means based on the power available he's got about... N minutes of power remaining. Still seems a stupidly annoying problem to solve with so many variables.
Comments (0)
No comments yet. Start the discussion.