Difference between revisions of "Talk:Software"
From TheAnalogThing
m |
(answering questions. did not notice them so far!) |
||
Line 1: | Line 1: | ||
− | I wonder if it would be useful to have a section on how best to document the wiring for a particular "program" (not sure what to call it) on the THAT? For example, how do you document that the output of Integrator 1 goes to the input of Summer 2? | + | == How to write down analog programs == |
+ | I wonder if it would be useful to have a section on how best to document the wiring for a particular "program" (not sure what to call it) on the THAT? For example, how do you document that the output of Integrator 1 goes to the input of Summer 2? --[[User:Brucekissinger]] | ||
− | I use Jupyter notebooks at work and was wondering if it would be useful to create a Jupyter notebook extension that could be used to show the wiring that is needed. I envision the notebook to be useful for documentation only and not suggesting that the notebook would directly execute something on the THAT device. But that would be a cool feature to add. | + | :Hi, |
+ | :The particular instances of the components are typically omitted, but it is quite trivial to add them to the circuit diagram. Take the ones of the [[Hindmarsh-Rose neuron model]] application: | ||
+ | : [[File:Hindmarsh rose prg.pdf|600px]] | ||
+ | :Consider the two multipliers. This diagram does not prescribe which multiplier has to be assigned to the two ones on THAT. But it is quite obvious that you could annotate one with a little <code>1</code> and one with a little <code>2</code> in the diagram. This is in fact the way how we denote individual computing elements. | ||
+ | :Best, --[[User:Sven|Sven]] ([[User talk:Sven|talk]]) 22:42, 16 December 2021 (CET) | ||
+ | |||
+ | == Jupyter notebooks == | ||
+ | I use Jupyter notebooks at work and was wondering if it would be useful to create a Jupyter notebook extension that could be used to show the wiring that is needed. I envision the notebook to be useful for documentation only and not suggesting that the notebook would directly execute something on the THAT device. But that would be a cool feature to add. --[[User:Brucekissinger]] | ||
+ | |||
+ | :This is in fact an interesting idea. If you want to produce something, we are eager to hear about it. Such a concept is worth one wiki page or two! --[[User:Sven|Sven]] ([[User talk:Sven|talk]]) 22:42, 16 December 2021 (CET) |
Latest revision as of 22:42, 16 December 2021
How to write down analog programs
I wonder if it would be useful to have a section on how best to document the wiring for a particular "program" (not sure what to call it) on the THAT? For example, how do you document that the output of Integrator 1 goes to the input of Summer 2? --User:Brucekissinger
- Hi,
- The particular instances of the components are typically omitted, but it is quite trivial to add them to the circuit diagram. Take the ones of the Hindmarsh-Rose neuron model application:
- Consider the two multipliers. This diagram does not prescribe which multiplier has to be assigned to the two ones on THAT. But it is quite obvious that you could annotate one with a little
1
and one with a little2
in the diagram. This is in fact the way how we denote individual computing elements. - Best, --Sven (talk) 22:42, 16 December 2021 (CET)
Jupyter notebooks
I use Jupyter notebooks at work and was wondering if it would be useful to create a Jupyter notebook extension that could be used to show the wiring that is needed. I envision the notebook to be useful for documentation only and not suggesting that the notebook would directly execute something on the THAT device. But that would be a cool feature to add. --User:Brucekissinger