Wikipedia:Reference desk/Mathematics: Difference between revisions

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
Content deleted Content added
Find the flaw: Let's hat the incorrect answer, too.
m Undid revision 768578306 by StuRat (talk) don't be an ass. Also, the OP has responded to Jayron's comment. Geez.
Line 107: Line 107:


The ratios of the sides are 1-1-sqrt(2). Sqrt(2) is irrational. However, in the real world, all lengths are an integer multiple of the [[Planck length]], proving that the sides must all be rational. Any flaw?? [[User:Georgia guy|Georgia guy]] ([[User talk:Georgia guy|talk]]) 00:19, 4 March 2017 (UTC)
The ratios of the sides are 1-1-sqrt(2). Sqrt(2) is irrational. However, in the real world, all lengths are an integer multiple of the [[Planck length]], proving that the sides must all be rational. Any flaw?? [[User:Georgia guy|Georgia guy]] ([[User talk:Georgia guy|talk]]) 00:19, 4 March 2017 (UTC)

{{hat}}


:[[False precision]]. In the real world, no measurement is infinitely reducible. You can draw any arbitrarily perfect isosceles triangle given the precision of the measuring device you use to verify it. That is, no real measuring device can tell the difference between a perfect and imperfect isosceles right triangle beyond a certain level of precision, which is good enough for the real world. --[[User:Jayron32|<span style="color:#009">Jayron</span>]][[User talk:Jayron32|<b style="color:#090">''32''</b>]] 00:40, 4 March 2017 (UTC)
:[[False precision]]. In the real world, no measurement is infinitely reducible. You can draw any arbitrarily perfect isosceles triangle given the precision of the measuring device you use to verify it. That is, no real measuring device can tell the difference between a perfect and imperfect isosceles right triangle beyond a certain level of precision, which is good enough for the real world. --[[User:Jayron32|<span style="color:#009">Jayron</span>]][[User talk:Jayron32|<b style="color:#090">''32''</b>]] 00:40, 4 March 2017 (UTC)
{{hat}}

::That's not what false precision is, as the article states. My bathroom scale that lists my weight to the tenth of a pound, but is only accurate to a pound, is an example of that. Then there's the joke: "He mister, how old is that dinosaur skeleton ?", "Well, it was 200 million years old when I started working at the museum, so now it would be 200 million and 7 years old". [[User:StuRat|StuRat]] ([[User talk:StuRat|talk]]) 00:46, 4 March 2017 (UTC)
::That's not what false precision is, as the article states. My bathroom scale that lists my weight to the tenth of a pound, but is only accurate to a pound, is an example of that. Then there's the joke: "He mister, how old is that dinosaur skeleton ?", "Well, it was 200 million years old when I started working at the museum, so now it would be 200 million and 7 years old". [[User:StuRat|StuRat]] ([[User talk:StuRat|talk]]) 00:46, 4 March 2017 (UTC)



Revision as of 17:45, 4 March 2017

Welcome to the mathematics section
of the Wikipedia reference desk.
Select a section:
Want a faster answer?

Main page: Help searching Wikipedia

   

How can I get my question answered?

  • Select the section of the desk that best fits the general topic of your question (see the navigation column to the right).
  • Post your question to only one section, providing a short header that gives the topic of your question.
  • Type '~~~~' (that is, four tilde characters) at the end – this signs and dates your contribution so we know who wrote what and when.
  • Don't post personal contact information – it will be removed. Any answers will be provided here.
  • Please be as specific as possible, and include all relevant context – the usefulness of answers may depend on the context.
  • Note:
    • We don't answer (and may remove) questions that require medical diagnosis or legal advice.
    • We don't answer requests for opinions, predictions or debate.
    • We don't do your homework for you, though we'll help you past the stuck point.
    • We don't conduct original research or provide a free source of ideas, but we'll help you find information you need.



How do I answer a question?

Main page: Wikipedia:Reference desk/Guidelines

  • The best answers address the question directly, and back up facts with wikilinks and links to sources. Do not edit others' comments and do not give any medical or legal advice.
See also:


February 26

Infantry squares field of fire

I was watching the film Waterloo last night. Really impressive battle scenes, nothing done with CGI, thousands of soviet soldiers used as extras apparently. I was wondering about the fields of fire from the British infantry squares which were formed when they were under cavalry attack. The squares are portrayed as being very close together and some seem to be directly firing on each other. See this still from the film. Is there a mathematical solution to the best orientation of the squares to avoid "friendly fire"? The solution is easy for a single line of soldiers, a line of diamond orientated squares like: ◇◇◇◇. However, in the film (and probably in reality as well) the squares extended to a depth of three or four lines. This is much more tricky to solve. Arbitrarily reducing the density of squares can produce a solution, but the density of squares has to be taken as fixed by the density of the troops while they were in-line formation. I don't believe any solution is possible for an arbitrary number of lines and infinite range of weapons, so the range of the rifles has to be taken as a parameter. Alternating rows of diamonds and squares works quite well,

◇   ◇   ◇   ◇
   ▢   ▢   ▢
◇   ◇   ◇   ◇

Rows of diamonds works even better for up to three rows if they can be spaced wide enough to allow the squares in the two rows behind to fire between them. That is a reasonable spacing on the assumption that the in-line length of the formation is 4× the side of the square.

◇    ◇    ◇    ◇
◇    ◇    ◇    ◇
◇    ◇    ◇    ◇

Is there a better solution? I guess this counts as a kind of packing problem. SpinningSpark 13:32, 26 February 2017 (UTC)[reply]

I guess the first question would be what do you mean by "better"? Are you're trying to pack the soldiers as densely as possible, do you want to maximize the area covered, or do you want to maximize the chances of winning a battle based on some model of combat? As you mentioned above, the range of the weapons has to be considered, but there are two parts to that. First, what is the effective range to hit your target, and second, how far can a shot be expected to travel and possibly hit an ally if it misses the enemy. Another factor would be how disciplined your soldiers are, since it's one thing to tell them to only shoot straight ahead, but it's another to have them actually do it when there's a armed horseman coming at them at an angle. Not having engaged in early 19th century warfare myself, I's sure there are many other realities of the situation that I simply can't imagine.
But if you reduce the problem to it's simplest possible form you might phrase it in terms of chess pieces. Namely, how many rooks and bishops can be placed on an nxn board without attacking one another? For rooks only the answer is trivially n. For bishops only it seems you can do a bit better - 4 on a 3x3 board, 6 on a 4x4 board and in fact the answer is known to be 2n-2, see [1]. --RDBury (talk) 01:45, 27 February 2017 (UTC)[reply]
One way to pack in more firepower without having them shoot each other is to fire from different heights. The front row would lie down, the 2nd row kneel, and the third row stand. Thus, the back rows fired over the heads of those in front. If they are prepared to fire to the rear, as well, that means 6 rows of soldiers, and perhaps more in the middle in support roles, such as replenishing ammunition, caring for the wounded, replacing fallen soldiers, etc. And if you have a natural elevation difference, such as a hill, even more rows can fire over the heads of those in front. StuRat (talk) 04:39, 27 February 2017 (UTC)[reply]
  • Not a mathematics answer, but my memories of The Mask of Command by John Keegan suggest me a hypothesis to the "friendly fire" question. (One big thesis of that book is that the increasing firearm range between Napoleon and the Civil War lead to a radically different style of command, because generals on the battlefield would be at a much higher risk of being targeted by sniper rifle in the latter than in the former.)
See Napoleonic_weaponry_and_warfare#Firearms: rifles only started to appear during the Napoleonic wars and were apparently reserved for semi-elite marksmen. The common soldier had a musket without rifling; from the various linked articles I gather that the effective range of non-rifled firearms was about 100-200 meters, after which the bullet deviated too much.
If friendly-fire casualties beyond 200m were negligible because almost all bullets would run in the ground or slow down too much by friction, separating the infantry squares by that distance would guarantee they could always shoot without any risk of hitting one another. TigraanClick here to contact me 12:41, 27 February 2017 (UTC)[reply]
We should also look at it strictly from a cost v. reward basis. The naive answer here is that if shooting in one direction is more likely to hit an enemy than your own forces, it's worth it. However, this would only work if both sides had equivalent forces. A more sophisticated formulation would be to say, if your side takes 1/10th the casualties of the enemy, due to superior equipment, tactics, training, numbers, etc., then you only want to fire if you are 10 times as likely to hit the enemy as your own forces. If course, this is only a rule of thumb, and specific situations will change that logic. For example, if an enemy is approaching with a bomb that could wipe out your entire infantry square, you'd better shoot at him, even if your own forces are directly behind him. StuRat (talk) 15:06, 27 February 2017 (UTC)[reply]
I'm not really looking for a practical military solution. If I was, I wouldn't have asked the question at this board. Perhaps I have not been clear enough. The problem is to devise a packing that maximises the perpendicular distance from the square edges to any other square while maintaining the overall density of troops equal to the in-line formation. Arbitrarily setting the squares 200 metres apart is therefore going outside the problem boundaries (and I believe it is also militarily impractical). The line density of troops in-line and in square edges should be assumed equal (or at least proportional). According to Line (formation) a line consisted of two to five ranks with three being most common, and, according to Infantry square, Wellington's squares at Waterloo were 500 men in four ranks in squares less than 20 metres on a side. A distance between lines is also needed. I have assumed this to be just enough to allow squares to form and have taken all lines to have the same number of ranks. SpinningSpark 15:17, 27 February 2017 (UTC)[reply]

March 1

Activity network question

Suppose that there are two activities emanating from the source node, A and B. There is one activity C, that depends on A alone; one, D, that depends on B alone; and one, E, that depends on A and B. It isn't obvious to me how to use a dummy in this case, so what do I do?--Leon (talk) 19:50, 1 March 2017 (UTC)[reply]

Can you add some context, and say what your objective is? (I'm familiar with dummy variables, but only in the context of regression.) Maybe you could give a similar example in which you can show how a dummy is used. Loraof (talk) 17:34, 2 March 2017 (UTC)[reply]
An ASCII text diagram may help:
                  E
                  ^
                  |
                  ^
                 / \
           C <- A   B -> D
StuRat (talk) 18:16, 2 March 2017 (UTC)[reply]
I think in the particular precedence chart style the OP is referring to (there are many), each task is represented by the edge of a directed graph and each node represents a possible stage of completion. Say node 0 is nothing done, 1 is A done, 2 is B done, 3 is A and B done, 4 is A and C done, 5 is B and D done, and 6 is A, B and E done, with other nodes to be filled in as more tasks are added to make a complete diagram. Then A connects 0 to 1, B connects 0 to 2, C connects 1 to 4, D connects 2 to 5, and E connect 3 to 6. So far there is nothing to show 3 is connected to 1 and 2, so you need two dummy tasks, say X to connect 1 and 3, and Y to connect 2 and 3. Not my area of of expertise (the whole field is pretty woolly if you ask me), but hopefully that helps. --RDBury (talk) 03:50, 3 March 2017 (UTC)[reply]

March 2

March Madness Auction

I've been invited to participate in an upcoming auction for the NCAA basketball tournament, in lieu of the typical fill-out-a-bracket, with rules roughly as follows:

  • Each team (final 64 only; play-in games are ignored) goes up for auction in a random order
  • Depending on the seed of the team, there's a minimum bid price (ranging from $1 to $20, but I don't know the specific distribution)
  • Each team must be sold
  • Payouts are based on the games that each team you own wins, as a percentage of the total pool of money spend buying teams, as follows: 1% for 1st round win; 1.5% for second; 2% for 3rd, 3% for 4th, 4% for 5th and 8% for winning the championship.
  • The total amount of the pool (and the number of players, though I think that's irrelevant) is, of course, unknown in advance.

With data for the likelihood that each team will reach each round in the tournament (which I can get from 538 or the like), I can calculate the expected percentage of the total pool that each team will win. What I don't know how to do is translate that info into an appropriate bid amount, since I won't know until the end what the total pool is.

To finally get to asking a question, any idea how I can get a plausible estimate for the "correct" amount to bid on each team? I could always just decide in advance what I think the total pool amount will be, but that's unlikely to be inaccurate and would lead to systematic over or under bidding, so I think I need some process (hopefully quick, since this'll be happening live) that could quickly update my total pool estimate (and thus my break even bid amount for each team) as each team is purchased. --Strohbot (talk) 23:03, 2 March 2017 (UTC)[reply]

EDIT: Should have googled first, but it turns out this is a thing with a name: Calcutta auction. So I guess my real question is, any information available for a bidding strategy for a Calcutta auction? --Strohbot (talk) 23:12, 2 March 2017 (UTC)[reply]

You should be able to estimate the number of total bidders there will be by the number who bid on earlier auctions. However, we get into game theory here, in that others may also take a wait-and-see approach to gauge the amount of bidders, too. So, it could end up like an Ebay auction, where it's pointless to bid until the last few seconds, as doing so gives away too much info. StuRat (talk) 04:00, 3 March 2017 (UTC)[reply]
Then there's historical data. That is, how many bidders were there last year, and what was the total payout ? Combining these two techniques, you could use the relative number of bids in last year's early auctions versus this year's. The random nature of the auction order does throw a bit of a monkey wrench into the works, but if the first half of the auctions have 10 times as many bidders as last year, you could reasonably assume the total payout will be around 10X last year's. StuRat (talk) 19:37, 3 March 2017 (UTC)[reply]

March 3

Excepting February alone ...

Overheard in a shop on Tuesday afternoon:

Customer - Today is the last day of February?

Shopkeeper - No - yes, next in four years' time!

What do people know about the lengths of the months, which years are leap years and the distance between them? This question was asked last year, but the discussion was derailed when one responder told another to get off my lawn. 86.128.236.125 (talk) 23:07, 3 March 2017 (UTC)[reply]

See perpetual calendar. You can tell which day will be which date for as long as we use our current calendar, because it follows a strict 400-year cycle of 14 possible years. --Jayron32 00:42, 4 March 2017 (UTC)[reply]


March 4

Find the flaw

This appears to prove it's impossible to draw a perfect isosceles right triangle:

The ratios of the sides are 1-1-sqrt(2). Sqrt(2) is irrational. However, in the real world, all lengths are an integer multiple of the Planck length, proving that the sides must all be rational. Any flaw?? Georgia guy (talk) 00:19, 4 March 2017 (UTC)[reply]

False precision. In the real world, no measurement is infinitely reducible. You can draw any arbitrarily perfect isosceles triangle given the precision of the measuring device you use to verify it. That is, no real measuring device can tell the difference between a perfect and imperfect isosceles right triangle beyond a certain level of precision, which is good enough for the real world. --Jayron32 00:40, 4 March 2017 (UTC)[reply]
This discussion has been closed. Please do not modify it.
The following discussion has been closed. Please do not modify it.
That's not what false precision is, as the article states. My bathroom scale that lists my weight to the tenth of a pound, but is only accurate to a pound, is an example of that. Then there's the joke: "He mister, how old is that dinosaur skeleton ?", "Well, it was 200 million years old when I started working at the museum, so now it would be 200 million and 7 years old". StuRat (talk) 00:46, 4 March 2017 (UTC)[reply]
Every time you speak, you verify your intelligence. --Jayron32 02:09, 4 March 2017 (UTC)[reply]
The same is true of you. As the first sentence in your link states: "False precision ... occurs when numerical data are presented in a manner that implies better precision than is justified; since precision is a limit to accuracy, this often leads to overconfidence in the accuracy as well." This applies to my examples, but not the the OP, as no numeric data has been presented, and there is no overconfidence in accuracy resulting from this. StuRat (talk) 04:48, 4 March 2017 (UTC)[reply]
If you've got a ruler with markings as small as a Planck length, I'd love to see it. --Jayron32 05:03, 4 March 2017 (UTC)[reply]
You still don't get it, so I will explain further. Had somebody reported the length of the edges of a drawn triangle in units beyond what they could measure, then that would be an example of false precision. But that has absolutely nothing to do with this question, as nobody made such a claim. StuRat (talk) 05:09, 4 March 2017 (UTC)[reply]
So, you mean like trying to draw a triangle and reporting it's size in units of Planck length, right? Like the OP asked?--Jayron32 13:22, 4 March 2017 (UTC)[reply]
No, they didn't ask about that at all. That would be false precision, as Planck length is LESS than the actual accuracy of a drawing, but they were complaining that Planck length is MORE than zero. StuRat (talk) 14:43, 4 March 2017 (UTC)[reply]
What is this level of precision; specifically its base 10 logarithm?? Has anyone proposed technology that will strengthen it?? Georgia guy (talk) 00:44, 4 March 2017 (UTC)[reply]
No flaw, it is impossible to draw one exactly. A bit silly to worry about it, though. StuRat (talk) 00:46, 4 March 2017 (UTC)[reply]
Why do you believe "in the real world, all lengths are an integer multiple of the Planck length"? (Not that freeing yourself from that common misunderstanding will allow for construction of infinitely precise physical objects.) -- ToE 05:40, 4 March 2017 (UTC)[reply]
That is more of a 'fat finger' type limit and applies to the sides of the triangle as well as the hypotenuse. One can't meaningfully point more accurately than that, and one can't add up some zillions of fat finger widths to get some precise length! Dmcq (talk) 12:06, 4 March 2017 (UTC)[reply]

theory of decomposition spaces

Can somebody tell me what this is and if we have an article or field about it on hand? It comes from this article: Georg Aumann. Thanks. scope_creep (talk) 12:56, 4 March 2017 (UTC)[reply]