Programming - Revision history

Jowan at 16:06, 10 March 2020

2020-03-10T16:06:32Z

← Older revision		Revision as of 16:06, 10 March 2020
Line 1:		Line 1:
	Setting standards and constraints first is a good idea.		Setting standards and constraints first is a good idea.

	These minibots are small small small and they have microprocessors built of dirt on an alien planet. I don't expect them to be powerful and I don't imagine they'll each have a lot of memory. The underlying architecture might as well be RISC-V since it's very well tested, can be low heat generating and it's open source.		These minibots are small small small and they have microprocessors built of dirt on an alien planet. I don't expect them to be powerful and I don't imagine they'll each have a lot of memory. The underlying architecture might as well be RISC-V since it's very well tested, can be low heat generating and it's open source. There's also a way into the design aspects at https://developer.arm.com/ip-products/designstart
	==Communications on site==		==Communications on site==
	Each minibot is autonomous and addressable, it has the project in mind and it decides what to do and who to do it with. The alternative is to build overseers.		Each minibot is autonomous and addressable, it has the project in mind and it decides what to do and who to do it with. The alternative is to build overseers.

Jowan at 08:19, 10 March 2020

2020-03-10T08:19:56Z

← Older revision		Revision as of 08:19, 10 March 2020
Line 1:		Line 1:
	Setting standards and constraints first is a good idea.		Setting standards and constraints first is a good idea.

	These minibots are small small small and they have microprocessors built of dirt on an alien planet. I don't expect them to be powerful and I don't imagine they'll each have a lot of memory.		These minibots are small small small and they have microprocessors built of dirt on an alien planet. I don't expect them to be powerful and I don't imagine they'll each have a lot of memory. The underlying architecture might as well be RISC-V since it's very well tested, can be low heat generating and it's open source.
	==Communications on site==		==Communications on site==
	Each minibot is autonomous and addressable, it has the project in mind and it decides what to do and who to do it with. The alternative is to build overseers.		Each minibot is autonomous and addressable, it has the project in mind and it decides what to do and who to do it with. The alternative is to build overseers.

John: Reverted edits by 120.20.219.54 (talk) to last revision by John

2020-01-30T04:57:26Z

Reverted edits by 120.20.219.54 (talk) to last revision by John

← Older revision	Revision as of 04:57, 30 January 2020
Line 1:	Line 1:
		Setting standards and constraints first is a good idea.

		These minibots are small small small and they have microprocessors built of dirt on an alien planet. I don't expect them to be powerful and I don't imagine they'll each have a lot of memory.
		==Communications on site==
		Each minibot is autonomous and addressable, it has the project in mind and it decides what to do and who to do it with. The alternative is to build overseers.

		Randomly picking a task at birth gives roughly the right proportions of task seekers as are needed. It's a lot easier than looking at a trillion neighbours all trying to work out what needs fixing next.

		Addresses. Let's solve this puzzle for the host as a whole, not just this single swarm. We can always step downward if we need to for practical reasons later.

		Mass of host as mols times Avogadro's constant / atoms per device = number of addresses needed given full conversion:

		3.3E23kg / 0.054 * 6E23 / 3.6E10 = 1E38 addresses

		which is roughly 2^117

		and we said 0.1% efficiency, = 1E35 addresses

		and we said 1% of host, =1E33 addresses.

		which is roughly 2^100, but both figures are under 2^128, which is a fair address length if we want a bit of slack. The length of an IPv6 address is 128 bits. Clearly someone's done this calculation ahead of me. IPv6 has approximately 3.4E38 addresses, so we have ourselves a viable addressing scheme. I suggest we find an unused reserved bit near the end (there appear to be at least 11) and set it to 1 so we can never clash with the Internet, since we're not going to apply for address space from a terrestrial net-master.

		I do not as yet know how an autonomous bot can self-assign a unique address. I don't think it can happen so we appear to need a full Internet implementation on site. Fortunately we don't have to re-invent that particular wheel. And yes, on reflection Jowan may well be right and we do need to build overseers after all. He'll be back online by Tuesday, just at the moment he has a cold. [[User:John\|John]] ([[User talk:John\|talk]]) 08:28, 12 January 2020 (UTC)

		==Communications Site/Earth==
		The NASA Lander report 2010 says: Landed operations assume 8 hours of contact per day using the Deep Space Network (DSN) 34-m dish.
		This will bring down an average of 100 Mbits of science data per day.

		Similar networks are run by Russia, China, India, Japan and the European Space Agency. We might outsource access to one. Creating a Deep Space Network for this one project would be an expensive distraction.

		==Overview==
		Two systems are needed for the payload to be delivered to the surface.

		#We need a command computer onboard, programmed to navigate and to communicate.
		#We also need a simulator to wrap around it, to get the first system tested. Once the command computer is in transit it has to work first time.

		There is a second phase system to run on the same hardware once the landing is complete. This is the establishment of ground operations and the site communications phase.

120.20.219.54: Blanked the page

2020-01-30T01:13:47Z

Blanked the page

← Older revision		Revision as of 01:13, 30 January 2020
Line 1:		Line 1:
	~~Setting standards and constraints first is a good idea.~~

	~~These minibots are small small small and they have microprocessors built of dirt on an alien planet. I don't expect them to be powerful and I don't imagine they'll each have a lot of memory.~~
	~~==Communications on site==~~
	~~Each minibot is autonomous and addressable, it has the project in mind and it decides what to do and who to do it with. The alternative is to build overseers.~~

	Randomly picking a task at birth gives roughly the right proportions of task seekers as are needed. It's a lot easier than looking at a trillion neighbours all trying to work out what needs fixing next.

	~~Addresses. Let's solve this puzzle for the host as a whole, not just this single swarm. We can always step downward if we need to for practical reasons later.~~

	~~Mass of host as mols times Avogadro's constant / atoms per device = number of addresses needed given full conversion:~~

	~~3.3E23kg / 0.054 * 6E23 / 3.6E10 = 1E38 addresses~~

	~~which is roughly 2^117~~

	~~and we said 0.1% efficiency, = 1E35 addresses~~

	~~and we said 1% of host, =1E33 addresses.~~

	which is roughly 2^100, but both figures are under 2^128, which is a fair address length if we want a bit of slack. The length of an IPv6 address is 128 bits. Clearly someone's done this calculation ahead of me. IPv6 has approximately 3.4E38 addresses, so we have ourselves a viable addressing scheme. I suggest we find an unused reserved bit near the end (there appear to be at least 11) and set it to 1 so we can never clash with the Internet, since we're not going to apply for address space from a terrestrial net-master.

	I do not as yet know how an autonomous bot can self-assign a unique address. I don't think it can happen so we appear to need a full Internet implementation on site. Fortunately we don't have to re-invent that particular wheel. And yes, on reflection Jowan may well be right and we do need to build overseers after all. He'll be back online by Tuesday, just at the moment he has a cold. [[User:John\|John]] ([[User talk:John\|talk]]) 08:28, 12 January 2020 (UTC)

	~~==Communications Site/Earth==~~
	~~The NASA Lander report 2010 says: Landed operations assume 8 hours of contact per day using the Deep Space Network (DSN) 34-m dish.~~
	~~This will bring down an average of 100 Mbits of science data per day.~~

	Similar networks are run by Russia, China, India, Japan and the European Space Agency. We might outsource access to one. Creating a Deep Space Network for this one project would be an expensive distraction.

	~~==Overview==~~
	~~Two systems are needed for the payload to be delivered to the surface.~~

	~~#We need a command computer onboard, programmed to navigate and to communicate.~~
	~~#We also need a simulator to wrap around it, to get the first system tested. Once the command computer is in transit it has to work first time.~~

	~~There is a second phase system to run on the same hardware once the landing is complete. This is the establishment of ground operations and the site communications phase.~~

John: /* Communications Site/Earth */

2020-01-26T15:35:02Z

Communications Site/Earth

← Older revision		Revision as of 15:35, 26 January 2020
Line 27:		Line 27:
	This will bring down an average of 100 Mbits of science data per day.		This will bring down an average of 100 Mbits of science data per day.

	Similar networks are run by Russia, China, India, Japan and the European Space Agency. We might outsource access to one.		Similar networks are run by Russia, China, India, Japan and the European Space Agency. We might outsource access to one. Creating a Deep Space Network for this one project would be an expensive distraction.

	==Overview==		==Overview==

John: /* Communications Site/Earth */

2020-01-26T15:34:28Z

Communications Site/Earth

← Older revision		Revision as of 15:34, 26 January 2020
Line 26:		Line 26:
	The NASA Lander report 2010 says: Landed operations assume 8 hours of contact per day using the Deep Space Network (DSN) 34-m dish.		The NASA Lander report 2010 says: Landed operations assume 8 hours of contact per day using the Deep Space Network (DSN) 34-m dish.
	This will bring down an average of 100 Mbits of science data per day.		This will bring down an average of 100 Mbits of science data per day.

			Similar networks are run by Russia, China, India, Japan and the European Space Agency. We might outsource access to one.

	==Overview==		==Overview==

John: /* Communications Site/Control */

2020-01-26T15:32:42Z

Communications Site/Control

← Older revision		Revision as of 15:32, 26 January 2020
Line 23:		Line 23:
	I do not as yet know how an autonomous bot can self-assign a unique address. I don't think it can happen so we appear to need a full Internet implementation on site. Fortunately we don't have to re-invent that particular wheel. And yes, on reflection Jowan may well be right and we do need to build overseers after all. He'll be back online by Tuesday, just at the moment he has a cold. [[User:John\|John]] ([[User talk:John\|talk]]) 08:28, 12 January 2020 (UTC)		I do not as yet know how an autonomous bot can self-assign a unique address. I don't think it can happen so we appear to need a full Internet implementation on site. Fortunately we don't have to re-invent that particular wheel. And yes, on reflection Jowan may well be right and we do need to build overseers after all. He'll be back online by Tuesday, just at the moment he has a cold. [[User:John\|John]] ([[User talk:John\|talk]]) 08:28, 12 January 2020 (UTC)

	==Communications Site/~~Control~~==		==Communications Site/Earth==
	The NASA Lander report 2010 says: Landed operations assume 8 hours of contact per day using the Deep Space Network (DSN) 34-m dish.		The NASA Lander report 2010 says: Landed operations assume 8 hours of contact per day using the Deep Space Network (DSN) 34-m dish.
	This will bring down an average of 100 Mbits of science data per day.		This will bring down an average of 100 Mbits of science data per day.

John at 15:32, 26 January 2020

2020-01-26T15:32:06Z

← Older revision		Revision as of 15:32, 26 January 2020
Line 22:		Line 22:

	I do not as yet know how an autonomous bot can self-assign a unique address. I don't think it can happen so we appear to need a full Internet implementation on site. Fortunately we don't have to re-invent that particular wheel. And yes, on reflection Jowan may well be right and we do need to build overseers after all. He'll be back online by Tuesday, just at the moment he has a cold. [[User:John\|John]] ([[User talk:John\|talk]]) 08:28, 12 January 2020 (UTC)		I do not as yet know how an autonomous bot can self-assign a unique address. I don't think it can happen so we appear to need a full Internet implementation on site. Fortunately we don't have to re-invent that particular wheel. And yes, on reflection Jowan may well be right and we do need to build overseers after all. He'll be back online by Tuesday, just at the moment he has a cold. [[User:John\|John]] ([[User talk:John\|talk]]) 08:28, 12 January 2020 (UTC)

			==Communications Site/Control==
			The NASA Lander report 2010 says: Landed operations assume 8 hours of contact per day using the Deep Space Network (DSN) 34-m dish.
			This will bring down an average of 100 Mbits of science data per day.

	==Overview==		==Overview==
	Two systems are needed for the payload to be delivered to the surface.		Two systems are needed for the payload to be delivered to the surface.

John at 15:30, 26 January 2020

2020-01-26T15:30:04Z

← Older revision		Revision as of 15:30, 26 January 2020
Line 2:		Line 2:

	These minibots are small small small and they have microprocessors built of dirt on an alien planet. I don't expect them to be powerful and I don't imagine they'll each have a lot of memory.		These minibots are small small small and they have microprocessors built of dirt on an alien planet. I don't expect them to be powerful and I don't imagine they'll each have a lot of memory.

	==Communications on site==		==Communications on site==
	Each minibot is autonomous and addressable, it has the project in mind and it decides what to do and who to do it with. The alternative is to build overseers.		Each minibot is autonomous and addressable, it has the project in mind and it decides what to do and who to do it with. The alternative is to build overseers.
Line 23:		Line 22:

	I do not as yet know how an autonomous bot can self-assign a unique address. I don't think it can happen so we appear to need a full Internet implementation on site. Fortunately we don't have to re-invent that particular wheel. And yes, on reflection Jowan may well be right and we do need to build overseers after all. He'll be back online by Tuesday, just at the moment he has a cold. [[User:John\|John]] ([[User talk:John\|talk]]) 08:28, 12 January 2020 (UTC)		I do not as yet know how an autonomous bot can self-assign a unique address. I don't think it can happen so we appear to need a full Internet implementation on site. Fortunately we don't have to re-invent that particular wheel. And yes, on reflection Jowan may well be right and we do need to build overseers after all. He'll be back online by Tuesday, just at the moment he has a cold. [[User:John\|John]] ([[User talk:John\|talk]]) 08:28, 12 January 2020 (UTC)

	==Overview==		==Overview==

	Two systems are needed for the payload to be delivered to the surface.		Two systems are needed for the payload to be delivered to the surface.

John at 15:29, 26 January 2020

2020-01-26T15:29:46Z

← Older revision		Revision as of 15:29, 26 January 2020
Line 4:		Line 4:

	==Communications on site==		==Communications on site==
	Each ~~device~~ is autonomous and addressable, it has the project in mind and it decides what to do and who to do it with. The alternative is to build overseers.		Each minibot is autonomous and addressable, it has the project in mind and it decides what to do and who to do it with. The alternative is to build overseers.

	Randomly picking a task at birth gives roughly the right proportions of task seekers as are needed. It's a lot easier than looking at a trillion neighbours all trying to work out what needs fixing next.		Randomly picking a task at birth gives roughly the right proportions of task seekers as are needed. It's a lot easier than looking at a trillion neighbours all trying to work out what needs fixing next.