Talk:1425: Tasks - Revision history

170.85.154.189: There is a tool for this.

2026-01-13T01:55:54Z

There is a tool for this.

172.68.22.108: problem presented in the comic was never just find a bird in a static photo

2025-04-24T03:56:01Z

problem presented in the comic was never just find a bird in a static photo

172.70.86.179 at 21:01, 13 March 2024

2024-03-13T21:01:12Z

162.158.151.152: /* GIS being "easy" */

2024-03-13T20:44:54Z

‎GIS being "easy"

162.158.90.24: Add link to Ornithology researchers page that made the technology

2024-01-17T22:32:45Z

Add link to Ornithology researchers page that made the technology

172.70.210.41: Bird Buddy and the AX Visio have made this technology a reality!

2024-01-17T22:24:22Z

Bird Buddy and the AX Visio have made this technology a reality!

172.71.94.28: Comment

2023-08-09T10:55:51Z

Comment

172.70.86.62 at 20:21, 10 November 2022

2022-11-10T20:21:00Z

172.70.115.29: /* GIS being "easy" */

2022-11-10T19:37:36Z

‎GIS being "easy"

172.70.230.89: Add comment

2022-11-01T04:56:38Z

Add comment

← Older revision		Revision as of 01:55, 13 January 2026
Line 67:		Line 67:

	The explanation of bird identification assumed that a static picture was all the information available to the app. There is no reason the app can't use additional data for this problem (as it does for problem 1). There are various ways the App could estimating range (stereo pictures, series of images with different focal lengths, distance sensors). Could use images beyond the visible range. Could use multiple frames or moving images to figure parallax, and help differentiate static from moving objects. (Sensors in the camera could indicate how the camera moved to inform interpretation of time based imaging.) All of these techniques were possible when the comic was posted, although they present interesting problems. I updated the explanation to try to expand the possibilities. Put in this comment in case what I put in the explanation wasn't clear. [[Special:Contributions/172.68.22.108\|172.68.22.108]] 03:56, 24 April 2025 (UTC)		The explanation of bird identification assumed that a static picture was all the information available to the app. There is no reason the app can't use additional data for this problem (as it does for problem 1). There are various ways the App could estimating range (stereo pictures, series of images with different focal lengths, distance sensors). Could use images beyond the visible range. Could use multiple frames or moving images to figure parallax, and help differentiate static from moving objects. (Sensors in the camera could indicate how the camera moved to inform interpretation of time based imaging.) All of these techniques were possible when the comic was posted, although they present interesting problems. I updated the explanation to try to expand the possibilities. Put in this comment in case what I put in the explanation wasn't clear. [[Special:Contributions/172.68.22.108\|172.68.22.108]] 03:56, 24 April 2025 (UTC)
		+
		+	It is funny that this tool from Simon Willison - just did this task - https://tools.simonwillison.net/is-it-a-bird, 01:55, 13 January 2026 (UTC)

← Older revision		Revision as of 03:56, 24 April 2025
Line 65:		Line 65:
	The rewrite of the explanation is really long overdue! If it's hard to start from scratch, someone could request GPT-4 to make a plan on how to update the article, and then use the ideas for inspiration {{unsigned ip\|162.158.151.152\|20:44, 13 March 2024}}		The rewrite of the explanation is really long overdue! If it's hard to start from scratch, someone could request GPT-4 to make a plan on how to update the article, and then use the ideas for inspiration {{unsigned ip\|162.158.151.152\|20:44, 13 March 2024}}
	:If you think it could do with a rewrite, rewrite it yourself. (Stay away from GPT, though, still likely to give an unsatisfactory explanation. If not downright hallucinating.) [[Special:Contributions/172.70.86.179\|172.70.86.179]] 21:01, 13 March 2024 (UTC)		:If you think it could do with a rewrite, rewrite it yourself. (Stay away from GPT, though, still likely to give an unsatisfactory explanation. If not downright hallucinating.) [[Special:Contributions/172.70.86.179\|172.70.86.179]] 21:01, 13 March 2024 (UTC)
		+
		+	The explanation of bird identification assumed that a static picture was all the information available to the app. There is no reason the app can't use additional data for this problem (as it does for problem 1). There are various ways the App could estimating range (stereo pictures, series of images with different focal lengths, distance sensors). Could use images beyond the visible range. Could use multiple frames or moving images to figure parallax, and help differentiate static from moving objects. (Sensors in the camera could indicate how the camera moved to inform interpretation of time based imaging.) All of these techniques were possible when the comic was posted, although they present interesting problems. I updated the explanation to try to expand the possibilities. Put in this comment in case what I put in the explanation wasn't clear. [[Special:Contributions/172.68.22.108\|172.68.22.108]] 03:56, 24 April 2025 (UTC)

← Older revision		Revision as of 21:01, 13 March 2024
Line 63:		Line 63:
	:Updated to add credit where credit is due, the research team in our reality that created the technology is the Cornell Lab of Ornithology in the Center for Avian Population Studies and Macaulay Library: https://ebird.org/about/staff -- No doubt if Ponytail was the lead the staff could've done it in half the time! [[Special:Contributions/162.158.90.24\|162.158.90.24]] 22:32, 17 January 2024 (UTC)		:Updated to add credit where credit is due, the research team in our reality that created the technology is the Cornell Lab of Ornithology in the Center for Avian Population Studies and Macaulay Library: https://ebird.org/about/staff -- No doubt if Ponytail was the lead the staff could've done it in half the time! [[Special:Contributions/162.158.90.24\|162.158.90.24]] 22:32, 17 January 2024 (UTC)

−	The rewrite of the explanation is really long overdue! If it's hard to start from scratch, someone could request GPT-4 to make a plan on how to update the article, and then use the ideas for inspiration	+	The rewrite of the explanation is really long overdue! If it's hard to start from scratch, someone could request GPT-4 to make a plan on how to update the article, and then use the ideas for inspiration {{unsigned ip\|162.158.151.152\|20:44, 13 March 2024}}
		+	:If you think it could do with a rewrite, rewrite it yourself. (Stay away from GPT, though, still likely to give an unsatisfactory explanation. If not downright hallucinating.) [[Special:Contributions/172.70.86.179\|172.70.86.179]] 21:01, 13 March 2024 (UTC)

← Older revision		Revision as of 20:44, 13 March 2024
Line 62:		Line 62:
	The year is 2024, and there is an ArsTechnica article about the problem in this comic now being solved. https://arstechnica.com/information-technology/2024/01/famous-xkcd-comic-comes-full-circle-with-ai-bird-identifying-binoculars/ [[Special:Contributions/172.70.210.41\|172.70.210.41]] 22:24, 17 January 2024 (UTC)		The year is 2024, and there is an ArsTechnica article about the problem in this comic now being solved. https://arstechnica.com/information-technology/2024/01/famous-xkcd-comic-comes-full-circle-with-ai-bird-identifying-binoculars/ [[Special:Contributions/172.70.210.41\|172.70.210.41]] 22:24, 17 January 2024 (UTC)
	:Updated to add credit where credit is due, the research team in our reality that created the technology is the Cornell Lab of Ornithology in the Center for Avian Population Studies and Macaulay Library: https://ebird.org/about/staff -- No doubt if Ponytail was the lead the staff could've done it in half the time! [[Special:Contributions/162.158.90.24\|162.158.90.24]] 22:32, 17 January 2024 (UTC)		:Updated to add credit where credit is due, the research team in our reality that created the technology is the Cornell Lab of Ornithology in the Center for Avian Population Studies and Macaulay Library: https://ebird.org/about/staff -- No doubt if Ponytail was the lead the staff could've done it in half the time! [[Special:Contributions/162.158.90.24\|162.158.90.24]] 22:32, 17 January 2024 (UTC)
		+
		+	The rewrite of the explanation is really long overdue! If it's hard to start from scratch, someone could request GPT-4 to make a plan on how to update the article, and then use the ideas for inspiration

← Older revision		Revision as of 22:32, 17 January 2024
Line 61:		Line 61:

	The year is 2024, and there is an ArsTechnica article about the problem in this comic now being solved. https://arstechnica.com/information-technology/2024/01/famous-xkcd-comic-comes-full-circle-with-ai-bird-identifying-binoculars/ [[Special:Contributions/172.70.210.41\|172.70.210.41]] 22:24, 17 January 2024 (UTC)		The year is 2024, and there is an ArsTechnica article about the problem in this comic now being solved. https://arstechnica.com/information-technology/2024/01/famous-xkcd-comic-comes-full-circle-with-ai-bird-identifying-binoculars/ [[Special:Contributions/172.70.210.41\|172.70.210.41]] 22:24, 17 January 2024 (UTC)
		+	:Updated to add credit where credit is due, the research team in our reality that created the technology is the Cornell Lab of Ornithology in the Center for Avian Population Studies and Macaulay Library: https://ebird.org/about/staff -- No doubt if Ponytail was the lead the staff could've done it in half the time! [[Special:Contributions/162.158.90.24\|162.158.90.24]] 22:32, 17 January 2024 (UTC)

← Older revision		Revision as of 22:24, 17 January 2024
Line 59:		Line 59:

	I think that, like in a number of other comic explanations, the explanation of the humour has given way to the technical exposition of the situation. What made me chuckle about this comic is the old adage in the software industry that: ''It takes 5% of the time to implement the first 95%, but 95% of time to complete the last 5%''. Even when experienced programmers correctly identify the difficult element of a problem and attempt to compensate for that difficulty in their implementation schedules, they can still be ''wildly'' off the mark. In this case, 60 years and counting... [[Special:Contributions/172.71.94.28\|172.71.94.28]] 10:55, 9 August 2023 (UTC)		I think that, like in a number of other comic explanations, the explanation of the humour has given way to the technical exposition of the situation. What made me chuckle about this comic is the old adage in the software industry that: ''It takes 5% of the time to implement the first 95%, but 95% of time to complete the last 5%''. Even when experienced programmers correctly identify the difficult element of a problem and attempt to compensate for that difficulty in their implementation schedules, they can still be ''wildly'' off the mark. In this case, 60 years and counting... [[Special:Contributions/172.71.94.28\|172.71.94.28]] 10:55, 9 August 2023 (UTC)
		+
		+	The year is 2024, and there is an ArsTechnica article about the problem in this comic now being solved. https://arstechnica.com/information-technology/2024/01/famous-xkcd-comic-comes-full-circle-with-ai-bird-identifying-binoculars/ [[Special:Contributions/172.70.210.41\|172.70.210.41]] 22:24, 17 January 2024 (UTC)

← Older revision		Revision as of 10:55, 9 August 2023
Line 57:		Line 57:
	:The GIS data is being looked at to determine if GPS-derived metadata lies within one of its boundaries, surely? Without GPS, the query has no sensible question to ask.		:The GIS data is being looked at to determine if GPS-derived metadata lies within one of its boundaries, surely? Without GPS, the query has no sensible question to ask.
	:(Then again, none of my own pictures have that sort of EXIF information. Either they're taken on a 'dumb' digital camera, that doesn't have inbuilt GPS, or even ''if'' they're done via my GPS+Camera-equipped tablet (rare) I've likely not allowed the one to be fed data that the other one knows. If it's even turned on. But the comic scenario clearly assumes otherwise.) [[Special:Contributions/172.70.86.62\|172.70.86.62]] 20:21, 10 November 2022 (UTC)		:(Then again, none of my own pictures have that sort of EXIF information. Either they're taken on a 'dumb' digital camera, that doesn't have inbuilt GPS, or even ''if'' they're done via my GPS+Camera-equipped tablet (rare) I've likely not allowed the one to be fed data that the other one knows. If it's even turned on. But the comic scenario clearly assumes otherwise.) [[Special:Contributions/172.70.86.62\|172.70.86.62]] 20:21, 10 November 2022 (UTC)
		+
		+	I think that, like in a number of other comic explanations, the explanation of the humour has given way to the technical exposition of the situation. What made me chuckle about this comic is the old adage in the software industry that: ''It takes 5% of the time to implement the first 95%, but 95% of time to complete the last 5%''. Even when experienced programmers correctly identify the difficult element of a problem and attempt to compensate for that difficulty in their implementation schedules, they can still be ''wildly'' off the mark. In this case, 60 years and counting... [[Special:Contributions/172.71.94.28\|172.71.94.28]] 10:55, 9 August 2023 (UTC)

← Older revision		Revision as of 20:21, 10 November 2022
Line 55:		Line 55:

	This comic is referring to doing a GIS lookup which is a glorified sql Query which has nothing to do with GPS and the the USGS spatial data a GIS database is commonly populated with is not derived from GPS information anyway. A GIS Lookup IS easy. Gathering the spatial data is difficult, though as previously mentioned its already widely and freely available for use. --[[User:PlatterMonkous\|PlatterMonkous]]		This comic is referring to doing a GIS lookup which is a glorified sql Query which has nothing to do with GPS and the the USGS spatial data a GIS database is commonly populated with is not derived from GPS information anyway. A GIS Lookup IS easy. Gathering the spatial data is difficult, though as previously mentioned its already widely and freely available for use. --[[User:PlatterMonkous\|PlatterMonkous]]
		+	:The GIS data is being looked at to determine if GPS-derived metadata lies within one of its boundaries, surely? Without GPS, the query has no sensible question to ask.
		+	:(Then again, none of my own pictures have that sort of EXIF information. Either they're taken on a 'dumb' digital camera, that doesn't have inbuilt GPS, or even ''if'' they're done via my GPS+Camera-equipped tablet (rare) I've likely not allowed the one to be fed data that the other one knows. If it's even turned on. But the comic scenario clearly assumes otherwise.) [[Special:Contributions/172.70.86.62\|172.70.86.62]] 20:21, 10 November 2022 (UTC)

← Older revision		Revision as of 19:37, 10 November 2022
Line 53:		Line 53:

	:And it took about five years since the comic was posted to get to that point...		:And it took about five years since the comic was posted to get to that point...
		+
		+	This comic is referring to doing a GIS lookup which is a glorified sql Query which has nothing to do with GPS and the the USGS spatial data a GIS database is commonly populated with is not derived from GPS information anyway. A GIS Lookup IS easy. Gathering the spatial data is difficult, though as previously mentioned its already widely and freely available for use. --[[User:PlatterMonkous\|PlatterMonkous]]

← Older revision		Revision as of 04:56, 1 November 2022
Line 51:		Line 51:

	now deep learning is common you not need research team and five years anymore		now deep learning is common you not need research team and five years anymore
		+
		+	:And it took about five years since the comic was posted to get to that point...