Commit Graph

1160 Commits

Author SHA1 Message Date
eccd865cf7 app: stacked_cores: 60-xx: new experiment that tries moving a value along a 4-core loop
it does this in a non-complementary way; and it doesn't get more than
about 0.60 amplification
2022-11-17 23:28:49 +00:00
e13ddbdc1f app: stacked_cores: complete more 59-xx runs 2022-11-17 09:45:19 +00:00
38aa677aad app: stacked_cores: complete some 59-xx runs
they don't look super insightful/promising.
2022-11-17 01:17:42 +00:00
a2a851b26f app: stacked_cores: 58-xx: try merging cores via a complementary buffer
results aren't any better than the earlier complementary buffers
2022-11-16 12:29:27 +00:00
9d4e245388 app: stacked_cores: new 58-xx sim which tries a complementary buffer into a pre-charged output 2022-11-11 22:59:57 +00:00
6e198caaa3 fix "reset" -> "set" typo in SR latch example 2022-11-11 05:28:54 +00:00
b7112fab86 app: stacked_cores: 57xx: do some runs where only one pos core is wired
into the output
2022-11-11 03:35:24 +00:00
ea6799b764 app: stacked_cores: new 57-xx experiment: complementary buffer with doubled inputs 2022-11-10 01:23:02 +00:00
4539cb18fe app: stacked_cores: 56-xx: complete a few more runs 2022-11-09 03:36:04 +00:00
7443599054 app: stacked_cores: new 56-xx sim for complementary logic using multiple input cores
like 53-xx, but with double the input cores, and a fixed 1:1 coupling.
it achieves 0.9x amplification at best.
- which is *better* than the 0.8 amplification we see with 53-xx when
  using 1:1 coupling, but not enough
- what if we try this idea with 3:1 winding? we can do that if we
  sandwhich each output _between_ its associated input.
2022-11-09 01:20:15 +00:00
df68100f82 app: stacked_cores: define a fork -> join sim
this is like 18xx, but better measured & with better control/coupling
wirings.

so far we don't have anything > 1.0x amp, but closer to 0.75x
2022-11-08 09:23:28 +00:00
be172d4371 remove the 'license' section
no need to state my ideals so in-your-face here. better to just omit any talk
of licensing, if i truly believe it to be irrelevant.
2022-11-07 03:19:53 -08:00
4407a8d3f7 app: stacked_cores: 53-xx: complete some more runs, including one where inputs are uncoupled 2022-11-07 02:46:24 -08:00
16525127a1 app: stacked_cores: 53-xx: complete a run which uses pos-windings != neg-windings 2022-11-05 18:54:10 -07:00
af4b5ffa32 app: stacked_cores: 53-xx: complete a 1:1 coupled buffer
slope is poor, hovering around a constant 0.75 transmission ratio.
2022-11-05 02:59:10 -07:00
1742172e6c app: stacked_cores: 53-xx: add a 5:1 buffer
it seems to under-transfer compared to the 3:1 buffers.
this *might* be an issue of drive current -- unclear.
2022-11-04 06:11:08 -07:00
3ebcc550a0 app: stacked_cores: 53-xx: better constrain the interpolation, and plot slope 2022-11-04 06:10:04 -07:00
373c80793f app: stacked_cores: improve the 52-xx plotting/interpolation
it's a little slow :-(
i'd guess the `score` function is the slowest part. can maybe get scipy
to do a dot-product for us?
2022-11-04 03:22:42 -07:00
df828b6299 app: stacked_cores: create a plot_53xx and refactor the surroundings
note that the interpolation is very BAD. i need to figure out better
sampling.
2022-11-03 21:21:07 -07:00
4023a67912 app: stacked_cores: ingest 53-xx buffer results 2022-11-03 20:26:17 -07:00
aee3796c29 app: stacked_cores: note about preservation 2022-11-03 05:46:58 -07:00
a45c0c4324 app: stacked_cores: new 53-xx run, where we buffer differential signals 2022-11-03 05:42:38 -07:00
47189dcc7e app: stacked_cores: 52-xx: complete more or gate parameterizations 2022-11-03 04:39:06 -07:00
70e14b4578 app: stacked_cores: 52-xx: sort the runs naturally (natsort) 2022-11-03 01:09:12 -07:00
a754b6e01d app: stacked_cores: 52-xx: capture more runs of existing or gates 2022-11-03 01:02:33 -07:00
286a267f75 app: stacked_cores: 52-xx: add some facilities for plotting 52-xx or gate runs
it's primitive; not the *best* results
2022-11-02 17:21:29 -07:00
ff68e57fa5 app: stacked_cores: 52-xx: collect the measurements into a db 2022-11-02 15:42:49 -07:00
87366cf473 app: stacked_cores: define an "or gate" sim + script for post-processing
extract transfer characteristics with e.g.
```
extract_meas.py ../../../out/applications/stacked_cores/52-or--0.0004rad-5000ctl_cond-20000coupling_cond-2000ps-100ps-3ctl-3coupling-3_1_winding-49999998976e0-drive- 2e-9 4e-9 8e-9
```
2022-11-01 00:11:50 -07:00
9d2fbf8b07 app: stacked_cores: expand the 48-xx run set 2022-10-31 20:49:11 -07:00
267a204e7e app: stacked_cores: complete some more 51-xx runs with variable winding ratios 2022-10-29 01:05:51 -07:00
fc0ce9f083 app: stacked_cores: 51-xx: try some higher-current variants; schedule some 5:1 and 7:1 inverter runs 2022-10-28 05:18:18 -07:00
0c7df48234 app: stacked_cores: 51-xx: complete some experiments using single-clock cascaded cores
i'm able to get 0.8x amplification between the first and the third core.
this is *less* than the amplification i got when cascading only one core
of the first, so not likely a good direction to pursue, though i haven't
yet explored that much of the parameter space.
2022-10-28 02:43:12 -07:00
12f286c3c7 app: stacked_cores: prototype a 3-core/1-cycle inverter (51-xx)
we vary the conductivities, as with 50-xx. the hope is that with a
multi-core approach like this we might get >> 1.0x amplification in the
unloaded setup, which we can place into a loaded circuit and deal with
the ~70% loading penalty.
2022-10-27 18:31:39 -07:00
9c17d3b45d app: stacked_cores: conclude 50-xx runs 2022-10-27 18:17:11 -07:00
57e12cbe32 app: stacked_cores: 50-xx: explore some more runs
got the amplification up to a bit over 0.3...
2022-10-26 08:08:15 -07:00
6af2d1d9e3 app: stacked_cores: complete some more 50-xx runs 2022-10-25 15:29:33 -07:00
cba2db6b10 app: stacked_cores: 50-xx: complete a run with high *control* conductivity, and schedule a few more 2022-10-25 05:37:54 -07:00
f4f672aab6 app: stacked_cores: fix 49-xx (now 50-xx) and run a few paramaterizations 2022-10-25 03:58:19 -07:00
3f54b25cf1 app: stacked_cores: define 49-xx: a *typo'd* multi-stage inverter with parameterized conductivities
in fact, M2 is initialized improperly: this actually acts as an
(overpowered) single-clock-cycle inverter.
2022-10-24 21:49:10 -07:00
3e331db374 app: stacked_cores: 48-xx: grab more detailed measurements for recent inverters 2022-10-24 06:53:03 -07:00
87e94d2182 app: stacked_cores: enable 0.001-level precision for current setting 2022-10-24 02:40:58 -07:00
21d41ff3d5 app: stacked_cores: 48-xx: run another 2e10 I parameterization 2022-10-24 02:37:05 -07:00
e526289fe9 app: stacked_cores: 48-xx: test the high-side of current for an already successful run 2022-10-24 00:26:37 -07:00
0e3212e624 app: stacked_cores: 48-xx: try a few more 10ns, 5e4 coupling cond runs 2022-10-23 21:04:43 -07:00
2b8c5d45c2 app: stacked_cores: finish a lower-current variant of the 48-xx 5e2/4e4 conductivity run 2022-10-22 08:05:13 -07:00
e1867ee541 app: stacked_cores: 48-xx: complete a very low control-conductivity run (2e2) 2022-10-22 05:37:34 -07:00
816d7edc38 app: stacked_cores: 48-xx: complete a few more runs with varied conductivity ratios 2022-10-22 01:24:18 -07:00
32c643ef13 app: stacked_cores: 48-xx: complete runs for 5e2/4e4 ctrl/coupling run
high slope (1.70) over a narrow domain
2022-10-21 20:33:51 -07:00
8a8823ffd8 app: stacked_cores: more 48-xx runs where we vary the coupling conductivity separate from the control conductivity 2022-10-21 19:19:55 -07:00
75a88887f0 app: stacked_cores: 48-xx: simulate a few more variants
got one with a 1.4x slope at the start.
that's novel across all inverters i've simulated to-date.
2022-10-21 09:54:20 -07:00