Posted: Tue May 26, 2009 10:10 pm
Why Tom, you don't trust simulations from the get go? I'm shocked.I prefer design where I can work out roughly what a circuit will do before I build it, and before I simulate.
a discussion forum for Polywell fusion
https://talk-polywell.org/bb/
Why Tom, you don't trust simulations from the get go? I'm shocked.I prefer design where I can work out roughly what a circuit will do before I build it, and before I simulate.
I'm not sure that matters one way or the other. If GCMs were better at predicting than a naive forecast, we could say "OK, you have a working physical model here." But they don't. And the bar for a physical model is so much higher than a stochastic forecast that it is somewhat shocking anyone could claim a GCM was a working example of the former.I believe you think that because some parameters in GCMs are determined stochastically (from data sets independent from, indeed of a completely different kind from the global temperature that is being predicted) therefore the model has no more validity than an arbitrary stochastic model.
The IPCC is set up by UN politicians, not just for them. Those politicians then pick the scientists (who, shockingly enough, tend to have views that support the politicians' agenda). This self-licking ice cream cone creates huge problems of credibility. The UN has lots of obvious problems like this, such as when Cuba, Syria or Sudan sit on the Human Rights Commission.The IPCC is a scientific organisation set up to advise politicians.
wikipedia wrote:The IPCC Panel is composed of representatives appointed by governments and organizations. Participation of delegates with appropriate expertise is encouraged. Plenary sessions of the IPCC and IPCC Working Groups are held at the level of government representatives
They seem much much more convincing than the pro-AGW evidence, much of which cannot even be examined because the authors won't release it (ABS#2?).Crertainly none of the anti-AGW vignettes posted here seem convincing when examined carefully.
I've done enough of the work to know the AGW case is very weak. It's a very informed opinion. I've read far more pro-AGW studies than anti-AGW. A large amount of questionable one-sided data and flawed assumptions is not better or more convincing than a small amount. Skepticism must be the rule, not the exception.Of course, replying to blog simplifications and slur by more blog simplifications and slur does not get us very far. To survey properly the relevant literature and come to a truly informed opinion takes time. But if you don't believe the scientific consensus then either you remain in a state of uncertainty, or you do this work.
Yes it is. The null hypothesis is that man's CO2 emissions are not creating a huge problem. AGW advocates have to prove that they are. If they can prove that, there are all sorts of actions that would logically follow. If they can't, we should do nothing.As for scientific proof. It is not a matter of null hypothesis vs something complex. Climate exists, CO2 clearly influences climate. the scientific question is how much,
No, assuming a problem exists without proof is invalid. You can't just reframe the issue as "does CO2 influence climate."Assuming that it is zero when that is clearly not true is invalid.
Of course I wouldn't! That's the whole point. Spending trillions of dollars without proof of an actual problem is a very bad idea.I don't believe you would be so set against this if it were not for the political ramifications.
I believe TI provides a PC compatible cross compiler, but I prefer assembly. I like the fact that there is not anything it can't do. Besides, when learning a new architecture, it's easier to see whats going on than it is in a higher level language. Nowadays, ram and rom aren't much of a problem, but when I first started programing microprocessors, they were a big problem. I managed to write a time clock program (including day of the week ) using only 256 bytes of rom, and using no RAM whatsoever ( In CDP 1802 machine code.) It made for a very tidy 4 chip design back in 1982 !tomclarke wrote:raingdave -
Yes - 2$ is cheap, now £1.30.
I have virtually given up using assembler (and particularly detested 80xx assembler the few times I met it). Do you have enough ROM/RAM resources for a compiler? Simon would probably argue you use FORTH - perhaps better than assembler. Don't forget if resources are limited that you always end up using twice as much ROM as you initially expect
Yeah, analog designs can be a pain in the bum. If I have to use high frequency analog circuits, I try to find something someone else has already worked the bugs out of and adapt it to whatever i'm trying to do. It also helps to read what Robert Pease has to say over at "Electronic Design" . That guy is D*mn smart ! He is an analog genius! (BSEE from MIT in 1961 !)tomclarke wrote: There are current-mode op-amps now with GHz bandwidth but I am not good enough at RF design to use them without hassle. (I could follow app notes with pcb layouts, given a spectrum analyser and time I could sort out problems, but I will avoid it if I can!). I prefer design where I can work out roughly what a circuit will do before I build it, and before I simulate. It is partly down to experience - I used not to be able to predict what designs up to 100kHz would do without building them. And sometimes they still surprise me.
Tom
The several times I've used it lead me to believe it is an extraordinarily tidy language, one only assembly can beat. I suppose 256 bytes of ROM might in some circumstances be better than 196 of ROM and 4 of RAM--what I expect that clock would map to in FORTH--but not usually I think.Such a thing would not be possible in "C" or "Forth" etc.
Yup. RCA CDP1802. It had 16 general purpose registers in it which is why I could get by without any ram. The other chips were 2716 eprom, and two 74ls373s to drive the seven segment display.TDPerk wrote:"It made for a very tidy 4 chip design back in 1982 ! "
Err.
I inquire too late, one was a uC, correct?
Yours, TDP, ml, msl, & pfpp
That's the first microprocessor that I learned how to build circuits with, plus it didn't require much in the way of support circuitry. A Z80, or a 6502 or even a 6800 type processor requires ram, rom, data latches, buffers, address decoders etc to get it to do anything useful. An 1802 could do the job with just one rom and two data latches!MSimon wrote:The 1802 was long of tooth in 1982. Although IIRC it was the only CMOS uP available at that time. Almost everything else was NMOS.
BTW the 1802 was excellent as a FORTH processor.
Did you ever look at what Sinclair did with the Z-80? He used the address lines to decode the keyboard. It was very slick. I may even have my old Sinclair in the junk some where.ravingdave wrote:That's the first microprocessor that I learned how to build circuits with, plus it didn't require much in the way of support circuitry. A Z80, or a 6502 or even a 6800 type processor requires ram, rom, data latches, buffers, address decoders etc to get it to do anything useful. An 1802 could do the job with just one rom and two data latches!MSimon wrote:The 1802 was long of tooth in 1982. Although IIRC it was the only CMOS uP available at that time. Almost everything else was NMOS.
BTW the 1802 was excellent as a FORTH processor.
I was drawing out the printed circuit board design by hand, and I wanted the smallest chip count I could get ! :) We processed the boards with UV light through an optical mask and used ferric chloride to etch them. The fewer the traces we had, the less trouble we had to deal with caused by bad etching or bad exposures.
I miss the old 1802, but we've got a lot better stuff nowadays. (CC1111)
David
Funny, I thought you took anything the UN's "scientific panels" as the be all, end all of scientific truth? Morner headed the UN intergovernmental panel on sea level change, so if your blind faith in the IPCC is any indication, you should be accepting Morners statements as gospel truth.tomclarke wrote:How to recognise SBS
Here is Morner's paper - a classic example of SBS:
http://www.junkscience.com/jan04/nils-morner_1.pdf
He says:
(1) observational data show sea level not rising over last Century
(2) IPCC got it wrong
You can detect the likelihood of SBS from the fact that more than half of his paper is rubbishing of IPCC based on selective quotation etc.
Check out the papers citations (from a respectable citation database indexed on the original paper, not junkscience). You immediately discover the team analysing the satellite data that Morner quotes, horrified at Morner's naive use of the data.
It turns out that (unlike everyone else in the field) he uses RAW satellite data instead of carefully checking for bias etc. Why is this no good? There are two major biasses is the data:
(1) progressive error due to altimeter degradation
(2) a step error when the satellite was switched to the backup altimeter
These effects have been carefully checked and cross-validated by the groups familiar with the satellite. After the necessary processing for these errors the resulting time sequence shows linear rise in sea levels.
The group dealing with the satellite data were very surprised that anyone would draw conclusions from raw data without first checking for necessary corrections etc. But in this case Morner clearly has an agenda which is not that of a scientist trying to get to the truth,
Best wishes, Tom
Well isn't that interesting.IntLibber wrote:Funny, I thought you took anything the UN's "scientific panels" as the be all, end all of scientific truth? Morner headed the UN intergovernmental panel on sea level change, so if your blind faith in the IPCC is any indication, you should be accepting Morners statements as gospel truth.
I don't feel I understand design properly unless I can do a paper design and have a good idea of how it will work. At most this needs a calculator.Quote:
I prefer design where I can work out roughly what a circuit will do before I build it, and before I simulate.
Why Tom, you don't trust simulations from the get go? I'm shocked.
Yes - fingers are very useful for anything above 50kHz. I would have thought board supply noise as you, though if it was 7474 double-clocking a good scope might be enough to see a possibly ringing clock signal? I guess it would not be obvious to see since digital edges always look horrible and difficult anyway to separate signal and ground bounce.I was actually hired to fix a problem with a PLL in a radio. It had stumped their guys for 6 months. It only stumped me for a month. It turned out their phase detector was double pulsing due to some sharp waveform edges to the 7474 phase detector. They had changed the board layout and a circuit that once worked stopped working (too much phase jitter). It turned out the old board had a bit of coax feeding the 7474 clock. About an inch or inch and a half. A couple of pF. Just enough to round the pulse edges and prevent double pulsing.
I had thought it was a bypass problem and had added bypass caps everywhere. When I got done trying that the board looked like it had a disease. Then I put my finger in the right place and - it worked. The rest of course was obvious.