I'm sorry I don't know but I recently came across this device which is I guess a complex mechnical trajectory tracker and I believe was the only device used to determine any corrections needed to steer the spacecraft: http://en.wikipedia.org/wiki/Voskhod_Spacecraft_%22Globus%22... .. It's definitely an interesting read.... and sorry again for not answering your question.
EDIT: So from what I understand this is how it worked: they would record their initial trajectory observations from the ground as the rocket was fired into space. They would then enter that data into the mechanical Globus or IMP which would track the rocket while it was circling around Earth. Russians could only visually track it while it was over their own space as they did not have bases all over the world. The Globus would make sure they weren't flying totally blind. It wasn't perfect, however, and as the spacecraft came back into their observable space they would have to make minor corrections on the Globus and then instructed the astronauts in the spacecraft which firing sequence to perform in order to stay on course.
Perhaps the idea that code can only be read and manipulated by an educated intellectual minority seemed a revoltingly bourgeoisie concept to those in charge at the time.
"Although the main purpose of DRAKON Editor is capturing and editing algorithmic knowledge, it can also be used to build programs." (http://drakon-editor.sourceforge.net/)
> I guess also, if it aids readability, why not just generate the charts from code, rather than the other way around?
Because it works like syntax highlighting. You don't ask "Why don't you write code black on white, and add colors later for reading aid?".
It's described as "2-dimensional" - I guess that means you set your calculation up as a spreadsheet, then it generates native code to run it at full speed.
Most soviet equipment I have seen (1980-1991) was programmed using plain Assembly or C. The Soviet Union manufactured its own version of the 8086 processor that worked with all popular compilers of that time. However I don't know about the 1970s era.
While this may be off topic, i am actually a lot more interested how they executed the project management part of the whole program.
The project management techniques in use today seem like they have been largely developed in the US aeronautics industry.
The soviet space program was inteed a complex task requiring coordination with large teams in different areas of development. Is anybody aware how they organize that? is the methodology documented somewhere?
>> "This language is also intended for using by non-programmers."
Hardly surprising the Russians created their own programming language (doubt this is available via open source). However positive to see they aimed it towards non programmers.
[+] [-] mladenkovacevic|13 years ago|reply
EDIT: So from what I understand this is how it worked: they would record their initial trajectory observations from the ground as the rocket was fired into space. They would then enter that data into the mechanical Globus or IMP which would track the rocket while it was circling around Earth. Russians could only visually track it while it was over their own space as they did not have bases all over the world. The Globus would make sure they weren't flying totally blind. It wasn't perfect, however, and as the spacecraft came back into their observable space they would have to make minor corrections on the Globus and then instructed the astronauts in the spacecraft which firing sequence to perform in order to stay on course.
[+] [-] aquarin|13 years ago|reply
[+] [-] jpwagner|13 years ago|reply
The idea seems nice at first, but you always end up back at traditional programming (http://drakon-editor.sourceforge.net/python/python.html#clas...). To think that this is for non-programmers is silly.
I guess also, if it aids readability, why not just generate the charts from code, rather than the other way around?
[+] [-] DanI-S|13 years ago|reply
[+] [-] m_for_monkey|13 years ago|reply
"Although the main purpose of DRAKON Editor is capturing and editing algorithmic knowledge, it can also be used to build programs." (http://drakon-editor.sourceforge.net/)
> I guess also, if it aids readability, why not just generate the charts from code, rather than the other way around?
Because it works like syntax highlighting. You don't ask "Why don't you write code black on white, and add colors later for reading aid?".
[+] [-] run4yourlives|13 years ago|reply
People tend to be visual, especially when they are in unfamiliar territory - which everyone is in when they are learning.
"Visual Programming" helps with learning, thus comprehension.
[+] [-] gaius|13 years ago|reply
[+] [-] dimitar|13 years ago|reply
Although some people dislike it a lot it is very nice for diagnostic reasons.
[+] [-] farseer|13 years ago|reply
[+] [-] bjornbm|13 years ago|reply
(I don't have anything but that Soviet era mosaic to back it up with.)
[+] [-] timurlenk|13 years ago|reply
The project management techniques in use today seem like they have been largely developed in the US aeronautics industry.
The soviet space program was inteed a complex task requiring coordination with large teams in different areas of development. Is anybody aware how they organize that? is the methodology documented somewhere?
[+] [-] vl|13 years ago|reply
[+] [-] blrblr|13 years ago|reply
[+] [-] trebuch3t|13 years ago|reply
http://www.ibiblio.org/apollo/links.html
[+] [-] sparknlaunch|13 years ago|reply
Hardly surprising the Russians created their own programming language (doubt this is available via open source). However positive to see they aimed it towards non programmers.
Are there any Drakon programmers on HN?
[+] [-] illicium|13 years ago|reply
[+] [-] myko|13 years ago|reply
[+] [-] exim|13 years ago|reply
[+] [-] zwadia|13 years ago|reply
[deleted]
[+] [-] unknown|13 years ago|reply
[deleted]
[+] [-] cicloid|13 years ago|reply
[+] [-] siculars|13 years ago|reply
[+] [-] gordian|13 years ago|reply