Wikipedia:Reference desk/Archives/Mathematics/2007 November 17
Mathematics desk | ||
---|---|---|
< November 16 | << Oct | November | Dec >> | November 18 > |
Welcome to the Wikipedia Mathematics Reference Desk Archives |
---|
The page you are currently viewing is an archive page. While you can leave answers for any questions shown below, please ask new questions on one of the current reference desk pages. |
November 17
editIntegration
editI need some help - what method would one use to evaluate the integral: ? Thanks. -- Sturgeonman (talk) 16:24, 17 November 2007 (UTC)
- Try the substitution . -- Meni Rosenfeld (talk) 17:08, 17 November 2007 (UTC)
- By the way, there is a "Show preview" button, and Help:Formula has some information about writing formulae. -- Meni Rosenfeld (talk) 17:11, 17 November 2007 (UTC)
- The substitution will work and you will have to decompose fractions. You can also do this one by parts as opposed to substituting like Meni said. And then you might need to do the second integral by parts again. Anyway, it comes out to .A Real Kaiser (talk) 19:05, 17 November 2007 (UTC)
- We prefer not to give final results for what may be homework questions. -- Meni Rosenfeld (talk) 21:50, 17 November 2007 (UTC)
- Alternatively, expand as a geometric series, integrate term by term, and recognize the Taylor series. Fredrik Johansson 20:14, 17 November 2007 (UTC)
- The easiest way seems to be to divide top and bottom by , then the expression to be integrated is of the form -du/u, giving -ln(u). A bit of manipulation gives the answer in its simplest form, with not a "by parts" in sight. 81.159.14.111 (talk) 12:46, 18 November 2007 (UTC)
Not clear. You have , but the numerator is not the derivative of the denominator. -- Meni Rosenfeld (talk) 12:58, 18 November 2007 (UTC)- Dividing top and bottom by gives . SmaleDuffin (talk) 16:57, 18 November 2007 (UTC)
- Right, I should work on my reading comprehension skills. -- Meni Rosenfeld (talk) 18:05, 18 November 2007 (UTC)
- Dividing top and bottom by gives . SmaleDuffin (talk) 16:57, 18 November 2007 (UTC)
- The easiest way seems to be to divide top and bottom by , then the expression to be integrated is of the form -du/u, giving -ln(u). A bit of manipulation gives the answer in its simplest form, with not a "by parts" in sight. 81.159.14.111 (talk) 12:46, 18 November 2007 (UTC)
Optimal initial interval for my algorithm
editThis is going to be relatively complicated, and probably long, but I think it's an interesting problem and the solution will help me run things faster. I'm relatively well-educated mathematically, but probability/statistics and I often don't get along, so that's the part you may need to help me with.
I have a function, , defined over that maps a real number to a boolean. It's monotonically decreasing, if that can be said of a boolean function. That is,
The function is expensive to evaluate, and I would like to evaluate it as few times as possible. Pretty much anything you could express here is orders of magnitude computationally cheaper than evaluating .
My algorithm finds within . It does so in two stages:
- Find an interval over which changes, that is, an and a such that and
- Repeatedly bisect this interval, evaluating the middle point and halving the interval each time, until . The estimate of is then .
Now, I'm pretty sure the second stage is as efficient as it can be. It will take
calls of the function , where and are the ends of the interval when we start the second stage.
So let's focus on the first stage for a moment. Here's how I've implemented it:
- The calling routine gives an estimate of and . Let's call these and
- I evaluate and . If they're different, move on to stage 2 right away, the initial interval has been found.
- If they're the same, we have to search for an interval. I'll only give you the algorithm for if they're both 1; the algorithm for if they're both 0 is analogous (though modified a little to ensure that we never evaluate a negative number). Set
- Evaluate . This was picked because it doubles the interval, . If is 0, then we've found an appropriate interval and can move on to the next stage. Otherwise, set , , increment by one, and repeat this step.
So I think this stage is also optimal, but I'll take suggestions for improving it if anyone has any.
Now we get to my question. I want to choose and well. It's a question of balancing the average number of function evaluations required for the two stages: too narrow an interval, and the first stage will take too long; too wide an interval, and the second stage will take too long.
Obviously if I'm given no information whatsoever about there's no good way to choose this interval. But I happen to know something about before we even start this algorithm. It's a normally distributed random variable with mean and variance . (Actually, it's not, it's a completely deterministic number, but I happen to have a model that predicts and gives an estimate of mean square error analogous to the variance of a normal distribution).
So, how do I pick and in such a way to minimize the total number of evaluations of , over both stages?
Thanks, moink (talk) 20:47, 17 November 2007 (UTC)
- The normal distribution gives some hints the 68-95-99.7 rule states that for a normal distribution, almost all values lie within 3 standard deviations of the mean. So you have a 99.7% chance of q lying in . So will give good estimate. You might also try with a 95% chance of q lieing in the range. --Salix alba (talk) 21:04, 17 November 2007 (UTC)
- Right, but that means that most of the time the interval will be too big. So the majority of the time, stage 1 wouldn't happen at all, but stage 2 would take longer than it would have, given a smaller interval. I'm looking for the initial interval that gives the optimum tradeoff between the two stages. moink (talk) 21:12, 17 November 2007 (UTC)
- Must q be nonnegative? If so, it is not clear how can it be (treated as) normally distributed. Do you mean, perhaps, that μ is large enough for the discrepancy to be insignificant? Or perhaps q is the absolute value of a normally distributed variable?
- Yes, q is non-negative. So obviously it's not really normally distributed. It's just the best approximation I have for it. I guess I can think of it as a truncated normal distribution, with the low end of the tail cut off.
- I'll comment that, since q is assumed to be normally distributed, neither of your two steps is optimal. If you know, say, that and , then you are dealing with the conditional distribution of q given . The optimal next evaluation point depends on all parameters, but I suspect that as , taking the median is optimal (as opposed to the mid-range).
- I also don't think that starting with two points, and , is optimal. You should start with a single point, see what it tells you (either or ) and continue from there.
- I have two versions of my algorithm: one that starts with an initial point, and another that starts with an initial interval. I wrote the second because I was frustrated watching the first run: it seemed like the better the guess for the initial point, the worse the algorithm performed. But that was before I developed the alternative model for q.
- Here's what I think is optimal as , : Start with . At every step, take the median of the probability distribution conditional on what you currently know about q. Evaluate f at that point, and take the appropriate interval based on the result.
- I haven't really thought about how to calculate the median, but it shouldn't be too hard. -- Meni Rosenfeld (talk) 22:08, 17 November 2007 (UTC)
- Ha! That's the part I probably am bad at. Ok, I understand your idea, and I think you're proabably right. Now I just have to calculate the median of a conditional normal distribution, i.e. a normal distribution truncated at one end or both.
- Actually, that depends on what you want to minimize. This minimizes the expected number of evaluations. Minimizing worst case is not really possible, since the worst case will always be unboundedly many evaluations. If you want something in between, a simple bisection might have merits, though you will have to define what it is exactly that you want.
- Yes, the expected number of evaluations is what I'm looking to minimize. I should have made this more clear. It's more complicated than I've made it out to be, but the simple version is that I need a whole lot of evaluations of over a range of , since f is really , where is a vector of parameters I have some control over. The plan is actually to vary to maximize .
- That actually makes a significant difference, since the results for different values of can be used together to make the search faster. If nothing else, at the very least you'll know that if and for some , then there's no more point in searching at — it can't maximize . Also, if is expected to be continuous or even just have any kind of autocorrelation, you should be able to use that information to further refine your search. —Ilmari Karonen (talk) 09:40, 19 November 2007 (UTC)
- It's actually not that simple. If we want to maximize , we need to use some algorithm for it, for example, gradient ascent (in particular if is concave). Depending on the algorithm, it can depend in all sorts of ways on the values of q at specific points. It may need to know the value of q at some point to some precision, even if it is known that the maximum is not achieved at that point.
- I agree with the main issue, though, that the nature of the problem suggests that we can do better than naively computing q for any input. For example, as we approach the maximum, we have a rough idea of what q is, so we should no longer treat it as normally distributed over the entire range of possibilities. Our required precision should also increase as we approach the maximum. Optimizing the maximization problem is harder, and depends on our assumptions regarding . -- Meni Rosenfeld (talk) 12:35, 19 November 2007 (UTC)
- That actually makes a significant difference, since the results for different values of can be used together to make the search faster. If nothing else, at the very least you'll know that if and for some , then there's no more point in searching at — it can't maximize . Also, if is expected to be continuous or even just have any kind of autocorrelation, you should be able to use that information to further refine your search. —Ilmari Karonen (talk) 09:40, 19 November 2007 (UTC)
- Yes, the expected number of evaluations is what I'm looking to minimize. I should have made this more clear. It's more complicated than I've made it out to be, but the simple version is that I need a whole lot of evaluations of over a range of , since f is really , where is a vector of parameters I have some control over. The plan is actually to vary to maximize .
- Needless to say, the minimal possible expected number of evaluations is directly related to the information theoretical entropy of the distribution. -- Meni Rosenfeld (talk) 22:15, 17 November 2007 (UTC)
- Ummm, sure, needless to say. Information theory is another one of my weak points. Thank you very much for your help, you've given me a direction to go. moink (talk) 22:37, 17 November 2007 (UTC)
- After reading information entropy, yes, that is indeed obvious. moink (talk) 22:53, 17 November 2007 (UTC)
- Must q be nonnegative? If so, it is not clear how can it be (treated as) normally distributed. Do you mean, perhaps, that μ is large enough for the discrepancy to be insignificant? Or perhaps q is the absolute value of a normally distributed variable?
- Right, but that means that most of the time the interval will be too big. So the majority of the time, stage 1 wouldn't happen at all, but stage 2 would take longer than it would have, given a smaller interval. I'm looking for the initial interval that gives the optimum tradeoff between the two stages. moink (talk) 21:12, 17 November 2007 (UTC)