= 27d567bc2d48d9f40e9ccc20ea370b15)
Eugine_Nier comments on Values vs. parameters - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (65)
If "parameter" were "instrumental value", that would mean you could set the parameter according to your values. That would be very similar to saying it was part of your values.
The notion of "value" vs. "instrumental value" is probably bankrupt. It's very similar to the dichotomy of "grounded symbol vs. dependent symbol". I talked about this in the section "Value is a network problem" of my regrettably long post on values.
In this particular case, I'm also presenting the option that "parameter" is something you can place logical constraints on, regardless of values. Like math: You can't say that believing that 1+1=3 is one of your values.
Answer to Wei Dai: It's a parameter you need to set to implement your values; but I don't know how you set it. That's the problem I'm pointing out. Resolving whether this was an instrumental value or not would solve the problem.
If I understand you correctly, you're thinking of utility functions as f(p,U), were U is the state of the universe and p is some parameter. Here f is your values and p is the parameter. If that's the case, I don't understand the distinction your making by separating out p, i.e., why not just work with F(U)=f(p,U). If there's uncertainty about the value of p, how is that different from uncertainty about your utility function?
That is the question posed by the original post. There is a long history of assuming that it makes sense to talk about using the same utility function with different parameters.