URGENT !! A nuclear plant near Minneapolis in th e U.S. state of Minnesota has leaked radioactive material fo r a second...

[John Larkin]

On Mon, 3 Apr 2023 08:07:59 -0000 (UTC), Jasen Betts
<usenet@revmaps.no-ip.org> wrote:

On 2023-04-01, Lamont Cranston <amdx62@gmail.com> wrote:
I have an Arduino PCB that has the usual tactile membrane switches with through hole solder on both sides of the pcb. I want to remove the switch with out damaging the pcb. I know it sounds easy but I can\'t heat and unsolder four
connections at the same time. I don\'t mind damaging the switch I\'m removing. I have an SMD hot air station, and could heat the pcb. Is the solder removable with reasonable hot air station temps? What temperature would you recommend? I don\'t want to over heat other pcb components.
I could also try heating the pcb and apply a solder iron to the joints and try to lift one side at a time.
I have a hand operated solder sucker, but don\'t expect that to remove enough solder to free the switch lead.
Just looking for the best procedure to preserve the board.

if your holes are large enough you could try desoldering tubes.
https://www.aliexpress.com/item/1005004200362252.html

they have a wall thickness of about 0.1mm so the leads need to be a
bit smaller than the hole.


The price suggests the build quality fairly accurately, you could
probably do better with a dispensing needle on a 10ml syringe body,
if you can find one the right size - needle needs to fit over the pin
and go through the hole.

Clever. Thin-wall teflon tubing might work too, especially for a lot
of pins.

 

[Fred Bloggs]

On Monday, April 3, 2023 at 10:05:09 AM UTC-4, a a wrote:

On Monday, 3 April 2023 at 15:40:53 UTC+2, Fred Bloggs wrote:
On Monday, April 3, 2023 at 6:32:52 AM UTC-4, Martin Brown wrote:
On 01/04/2023 15:00, Fred Bloggs wrote:
On Saturday, April 1, 2023 at 1:05:21 AM UTC-4, Jan Panteltje wrote:
Ultrasonic sounds from plants, plants speaking at 40 kHz to 80 kHz
https://www.sciencedaily.com/releases/2023/03/230330133551.htm

The plants are not speaking at all. Sounds caused by cavitation effects as internal water columns drain due to dehydration is not speaking.
They might just possibly be communicating with insects - saying words to
the effect of \"Go away - I\'m toxic\". But I don\'t see an obvious
mechanism for them to generate such ultrasonic clicks though.

Capillary effects in xylem are strong enough to support very tall
columns of water as tall trees demonstrate so well.
Pretty sure they were talking about the herbaceous forb variety, not ligneous.



--
Martin Brown
Another fake research paper

Being Chinese you would know all about that.

 

[Simon S Aysdie]

On Sunday, April 2, 2023 at 9:57:20 AM UTC-7, Ralph Mowery wrote:

Can anyone recommend a PIN diode that can be used for up to switching a
RF amplifier in and out of the transmission line at 150 MHz and 450 MHz.

The powewr level ia 50 watts RF.

I haven\'t looked for awhile, but check Macom. They bought Metelics too, so they have a lot of stuff.

Skyworks had some stuff too, but less of a selection.

I was looking into stuff at that power, but higher frequency. Chip\'n\'wire microcircuit stuff. But these companies have the diodes.

 

[John Robertson]

On 2023/04/01 10:02 a.m., John Larkin wrote:

On Sat, 1 Apr 2023 09:55:01 -0700, John Robertson <jrr@flippers.com
wrote:

On 2023/04/01 9:10 a.m., John Larkin wrote:
I\'m writing a program to create a CSV file that lists possible
resistor matrix values. I might hand it off to other people to use. I
don\'t use spreadsheets so don\'t know much about them.

I can do lines with numbers and strings and commas, but I\'d like the
spreadsheets to start with introductory comments. So, how does one
format comments into a csv file?


Just type the comments into the cells where you want them located. Then
Merge the underlying (any cells covered by the comment) cells so only
one cell is around the comment to make it tidier.

The math only acts on the cells you tell it to, so comments, headings,
etc do not matter to the data.

John :-#)#

I guess so. Seems primitive.

KISS or possibly RTFM?

(ducking)

John ;-#)#

 

[Lamont Cranston]

OP
Here is a picture of the pcb showing the holes where the 3 switches were removed.
https://www.dropbox.com/s/tewq0en2ufnsipg/Switches%20removed.jpg?dl=0
Nice clean holes. Just like we all want.
Mikek

 

[Commander Kinsey]

On Mon, 27 Mar 2023 17:55:51 +0100, Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:

Commander Kinsey <CK1@nospam.com> wrote:

I have a centre tapped transformer I wanted to get the most power out of.
Thinking a traditional full wave rectifier (just a diode on each side,
calling the centre tap 0V at the output) is only running current through
one half of the secondary at a time, which is inefficient (think of
P=i^2R), I thought about putting a bridge rectifier on each half, then
connecting the result in parallel. I made the following diagram by
adjusting someone else\'s, so it may look a bit odd.

https://i.imgur.com/d2TfZYO.jpg

I\'m a bit confused here because you can trace the current flow and show
the output has both 24V (if the current goes through the \"wrong\" bridge on
the way back) and 12V at the same time, which isn\'t possible. Can someone
explain what would happen in this circuit?

Any way to make this work? I want current flowing through both halves of
the secondary all the time. But I want half the full secondary\'s voltage.

There is nothing you can do to increase the power if your load is
resistive - but if it is smoothed with a capacitor, there might be.

Using a choke between the rectifiers and the first smoothing capacitor
will even-out the current peaks through the transformer windings and
reduce the losses which are proportional to the square of the current.
You may then be able to run the transformer at a higher current than the
\'official\' rating, which is usually specified for peaky rectified
current.

The output voltage will then be approximately the RMS voltage of the
waveform (minus diode drops, the transformer winding resistance losses
and the choke resistance losses), not the rectified peak voltage. (minus
diode drops and somewhat larger transformer winding resistance loses).
Whether this ultimately equates to more *power*, rather than just more
current, will depend on the parameters of transformer and choke.

So not as easy as just adding a choke?

Yes it is rectified and smoothed. Bridge rectifier and massive capacitor.

Another way to increse the power handling of an particlar size of
transformer is to increase the frequency. This may not be practical for
a mains transformer - and you will soon run into greater losses from
eddy currents in the core at higher frequencies - but it is commonly
used to reduce the size and weight of transformers in aircraft.

I was thinking of how to use a bridge on each half then put both in parallel, but because they are currently (oh dear) in series, I think it\'s impossible.

So I got nasty. I\'ve hacked into the coils and changed it into three sets of unconnected coils. Which I then paralleled and bridge rectified and smoothed. Got a nice 60 amps, but the voltage change from open circuit to full load is too high. I\'m going to try a large capacitor, as there\'s quite a ripple.

It\'s destination is to power many GPUs which want 11.6V to 12.6V. The load on the transformer can vary dramatically as they process data or not.

 

[Commander Kinsey]

On Mon, 27 Mar 2023 18:55:25 +0100, John Larkin <jlarkin@highlandsnipmetechnology.com> wrote:

On Mon, 27 Mar 2023 17:55:51 +0100, liz@poppyrecords.invalid.invalid
(Liz Tuddenham) wrote:

Commander Kinsey <CK1@nospam.com> wrote:

I have a centre tapped transformer I wanted to get the most power out of.
Thinking a traditional full wave rectifier (just a diode on each side,
calling the centre tap 0V at the output) is only running current through
one half of the secondary at a time, which is inefficient (think of
P=i^2R), I thought about putting a bridge rectifier on each half, then
connecting the result in parallel. I made the following diagram by
adjusting someone else\'s, so it may look a bit odd.

https://i.imgur.com/d2TfZYO.jpg

I\'m a bit confused here because you can trace the current flow and show
the output has both 24V (if the current goes through the \"wrong\" bridge on
the way back) and 12V at the same time, which isn\'t possible. Can someone
explain what would happen in this circuit?

Any way to make this work? I want current flowing through both halves of
the secondary all the time. But I want half the full secondary\'s voltage.

There is nothing you can do to increase the power if your load is
resistive - but if it is smoothed with a capacitor, there might be.

Using a choke between the rectifiers and the first smoothing capacitor
will even-out the current peaks through the transformer windings and
reduce the losses which are proportional to the square of the current.
You may then be able to run the transformer at a higher current than the
\'official\' rating, which is usually specified for peaky rectified
current.

The output voltage will then be approximately the RMS voltage of the
waveform

Average is 2/pi times peak, which is a bit less.


(minus diode drops, the transformer winding resistance losses
and the choke resistance losses), not the rectified peak voltage. (minus
diode drops and somewhat larger transformer winding resistance loses).
Whether this ultimately equates to more *power*, rather than just more
current, will depend on the parameters of transformer and choke.

Another way to increse the power handling of an particlar size of
transformer is to increase the frequency. This may not be practical for
a mains transformer - and you will soon run into greater losses from
eddy currents in the core at higher frequencies - but it is commonly
used to reduce the size and weight of transformers in aircraft.

Power handling of a transformer or resistor or inductor improves with
air flow or heat sinking. They are usually specified in still air.

Good idea, I shall add those accordingly, got loads of heatsinks and fans kicking about.

Can I do the same with a SMPS? Mind you they\'re probably limited so I\'d need to alter the circuit.

 

[Carlos E.R.]

On 2023-04-03 11:29, Don Y wrote:

On 4/3/2023 1:08 AM, Carlos E.R. wrote:
I used to track key parameters of my workstations in a
text table (which is effectively a spreadsheet).  I figured
I could manually enumerate the boards in each, type of
GPU, CPU, amount (and type) of RAM, MAC, assigned IP, etc.

This worked fine -- when I had 6 workstations.  \"Fits on a
single sheet of paper\".

But, recently decided I should be doing the same with all of
my machines.  *Doesn\'t* fit on a single sheet of paper!

All but the smallest machines have at least two physical CPUs.
So, two columns for that.  And, I\'ll need to add a column
to indicate the number of cores in each (assuming them
to be identical).

Similarly, all but the smallest have at least 4 disks -- and
two or more optical drives.  So, at least 6 columns for that.

You can figure out a way to do that without columns ;-)

Not in a spreadsheet.  Unless you treat the spreadsheet as a text table
and all of the data as typeless.

In which case, why aren\'t you just using a word processor?  And, living
with the inevitable mistakes that will creep into your data?  E.g., l00
is not a number -- despite looking like one!

In a database (\"relation\") you can \"relate\" different tables to each other.
So, in addition to 1:1 relationships (implicit in a spreadsheet), you can
have 1:1, 1:n, n:m, n:1, etc. relationships, as dictated by the data.

Just write several lines.

Everybody knows how to do a spreadsheet, but not everybody knows how
to do a database.

Before there were spreadsheets, no one knew how to \"do\" them.
Visual tools are hardly more involved than those of a spreadsheet
(for flat relations).

You may not have database software. I think that M$ Office did not
always include it. And LO Base is not that intuitive.

Most have visual \"front ends\" that you can use -- making the
relations *look* like tables (spreadsheets).

And, it\'s commonplace to have a DBMS put constraints on data
in ways that spreadsheets can\'t/don\'t.  As well as having a wider
range of data types (how do you store a MAC in a spreadsheet?)

Infinite ways. As text, for example. As a huge number.

The reason you want \"typed\" fields is to reduce errors.
Is this a number: THIS
Is this a MAC:   HeLlOboysandgirls
Is this a float:  123.456.78,,90

A MAC is just a long hexadecimal number that is displayed differently.
I\'m sure it can be done if the sheet software can handle hex. Mine doesn\'t.

DBMSs present so many richer ways of presenting and preserving
data to make the DBAs job easier.

What do you do when there are two entries in a spreadsheet that
obviously refer to the same thing?  E.g., a part number having
two different descriptions?  In a DBMS, you can ensure that
all part numbers are unique (trying to add another record with
an existing part number throws an error).   You can also encode
other criteria to safeguard the data going into the relation.
E.g., \"biological child\'s age must be less than age of parents\"
(duh!) or \"birthdate must be in the past\", etc.

Try some simple problems in a spreadsheet... like keeping track
of the songs in your music collection.  Then, try to convince
yourself that your spreadsheet is better than just a textual table!

Or, document your family tree for a couple of generations.

I keep my \"list of books\" as a database with several related tables. I\'m
tempted to migrate to an spreadsheet, because, for instance, I can thus
carry it in my phone.

--
Cheers, Carlos.

 

[Ari Fin]

https://sulthanmesinpaving.com/tag/mesin/
https://sulthanmesinpaving.com/tag/cetak/
https://sulthanmesinpaving.com/tag/batako/
https://sulthanmesinpaving.com/tag/rh1s12/
https://sulthanmesinpaving.com/tag/paving/
https://sulthanmesinpaving.com/tag/surabaya/
https://sulthanmesinpaving.com/tag/block/
https://sulthanmesinpaving.com/tag/hidrolis/
https://sulthanmesinpaving.com/tag/mojokerto/
https://sulthanmesinpaving.com/tag/hidrolik/
https://sulthanmesinpaving.com/tag/otomatis/
https://sulthanmesinpaving.com/tag/kediri/
https://sulthanmesinpaving.com/tag/nusa-dua/
https://sulthanmesinpaving.com/tag/bali/
https://sulthanmesinpaving.com/tag/jual/
https://sulthanmesinpaving.com/tag/batam/
https://sulthanmesinpaving.com/tag/mesin-paving-batam/
https://sulthanmesinpaving.com/tag/mesin-paving-banyuwangi/
https://sulthanmesinpaving.com/tag/banyuwangi/
https://sulthanmesinpaving.com/tag/mejayan/
https://sulthanmesinpaving.com/tag/madiun/
https://sulthanmesinpaving.com/tag/mesin-cetak-batako-mejayan-madiun/
https://sulthanmesinpaving.com/tag/mesin-paving-block-mejayan-madiun/
https://sulthanmesinpaving.com/tag/mesin-cetak-paving-block-bojonegoro/
https://sulthanmesinpaving.com/tag/bojonegoro/
https://sulthanmesinpaving.com/tag/mesin-cetak-batako-paving-blitar/
https://sulthanmesinpaving.com/tag/blitar/
https://sulthanmesinpaving.com/tag/mesin-paving-multiblock-ponorogo/
https://sulthanmesinpaving.com/tag/ponorogo/
https://sulthanmesinpaving.com/tag/bondowoso/
https://sulthanmesinpaving.com/tag/mesin-paving-bondowoso/
https://sulthanmesinpaving.com/tag/mesin-paving-magetan/
https://sulthanmesinpaving.com/tag/magetan/
https://sulthanmesinpaving.com/tag/ngawi/
https://sulthanmesinpaving.com/tag/mesin-paving-ngawi/
https://sulthanmesinpaving.com/tag/mesin-paving-gresik/
https://sulthanmesinpaving.com/tag/gresik/
https://sulthanmesinpaving.com/tag/mesin-paving-probolinggo/
https://sulthanmesinpaving.com/tag/mesin-paving-nganjuk/
https://sulthanmesinpaving.com/tag/nganjuk/
https://sulthanmesinpaving.com/tag/mesin-paving-trenggalek/
https://sulthanmesinpaving.com/tag/trenggalek/
https://sulthanmesinpaving.com/tag/mesin-paving-malang/
https://sulthanmesinpaving.com/tag/malang/
https://sulthanmesinpaving.com/tag/mesin-paving-sidoarjo/
https://sulthanmesinpaving.com/tag/sidoarjo/
https://sulthanmesinpaving.com/tag/mesin-paving-tulungagung/
https://sulthanmesinpaving.com/tag/mesin-paving-jember/
https://sulthanmesinpaving.com/tag/jember/

 

[Ari Fin]

https://informasisiang.blogspot.com/2023/04/google-groups-karya-larry-page-dan.html

 

[John Larkin]

On Mon, 03 Apr 2023 22:12:31 +0100, \"Commander Kinsey\"
<CK1@nospam.com> wrote:

On Mon, 27 Mar 2023 18:55:25 +0100, John Larkin <jlarkin@highlandsnipmetechnology.com> wrote:

On Mon, 27 Mar 2023 17:55:51 +0100, liz@poppyrecords.invalid.invalid
(Liz Tuddenham) wrote:

Commander Kinsey <CK1@nospam.com> wrote:

I have a centre tapped transformer I wanted to get the most power out of.
Thinking a traditional full wave rectifier (just a diode on each side,
calling the centre tap 0V at the output) is only running current through
one half of the secondary at a time, which is inefficient (think of
P=i^2R), I thought about putting a bridge rectifier on each half, then
connecting the result in parallel. I made the following diagram by
adjusting someone else\'s, so it may look a bit odd.

https://i.imgur.com/d2TfZYO.jpg

I\'m a bit confused here because you can trace the current flow and show
the output has both 24V (if the current goes through the \"wrong\" bridge on
the way back) and 12V at the same time, which isn\'t possible. Can someone
explain what would happen in this circuit?

Any way to make this work? I want current flowing through both halves of
the secondary all the time. But I want half the full secondary\'s voltage.

There is nothing you can do to increase the power if your load is
resistive - but if it is smoothed with a capacitor, there might be.

Using a choke between the rectifiers and the first smoothing capacitor
will even-out the current peaks through the transformer windings and
reduce the losses which are proportional to the square of the current.
You may then be able to run the transformer at a higher current than the
\'official\' rating, which is usually specified for peaky rectified
current.

The output voltage will then be approximately the RMS voltage of the
waveform

Average is 2/pi times peak, which is a bit less.


(minus diode drops, the transformer winding resistance losses
and the choke resistance losses), not the rectified peak voltage. (minus
diode drops and somewhat larger transformer winding resistance loses).
Whether this ultimately equates to more *power*, rather than just more
current, will depend on the parameters of transformer and choke.

Another way to increse the power handling of an particlar size of
transformer is to increase the frequency. This may not be practical for
a mains transformer - and you will soon run into greater losses from
eddy currents in the core at higher frequencies - but it is commonly
used to reduce the size and weight of transformers in aircraft.

Power handling of a transformer or resistor or inductor improves with
air flow or heat sinking. They are usually specified in still air.

Good idea, I shall add those accordingly, got loads of heatsinks and fans kicking about.

Can I do the same with a SMPS? Mind you they\'re probably limited so I\'d need to alter the circuit.

Yes, air flow increases the power capability of most things. Resistors
can be run at 1.5 to as much as 5x rated power with a lot of air. This
is usually best determined by testing.

A flyback power supply may never put out much more than design
power... probably not cooling limited.

 

[Lenny Raha]

https://sulthanmesinpaving.com/tag/pacitan/
https://sulthanmesinpaving.com/tag/mesin-paving-pacitan/
https://sulthanmesinpaving.com/tag/mesin-paving-jombang/
https://sulthanmesinpaving.com/tag/jombang/
https://sulthanmesinpaving.com/tag/mesin-paving-lamongan/
https://sulthanmesinpaving.com/tag/lamongan/
https://sulthanmesinpaving.com/tag/mesin-paving-tuban/
https://sulthanmesinpaving.com/tag/tuban/

 

[Don Y]

On 4/3/2023 2:30 PM, Carlos E.R. wrote:

Not in a spreadsheet.  Unless you treat the spreadsheet as a text table
and all of the data as typeless.

In which case, why aren\'t you just using a word processor?  And, living
with the inevitable mistakes that will creep into your data?  E.g., l00
is not a number -- despite looking like one!

In a database (\"relation\") you can \"relate\" different tables to each other.
So, in addition to 1:1 relationships (implicit in a spreadsheet), you can
have 1:1, 1:n, n:m, n:1, etc. relationships, as dictated by the data.

Just write several lines.

So, you have to be able to embed a newline in the field -- or, some other
delimiter to separate list elements (that won\'t, itself, be present in
any of the elements).

And, the \"type\" of the field now needs to be \"list of _____\" (instead
of just \"_____\").

Or, you deal with simple text and hope anything that consumes the data
won\'t gag on an undiscovered error in the data (!)

And, it\'s commonplace to have a DBMS put constraints on data
in ways that spreadsheets can\'t/don\'t.  As well as having a wider
range of data types (how do you store a MAC in a spreadsheet?)

Infinite ways. As text, for example. As a huge number.

The reason you want \"typed\" fields is to reduce errors.
Is this a number: THIS
Is this a MAC:   HeLlOboysandgirls
Is this a float:  123.456.78,,90

A MAC is just a long hexadecimal number that is displayed differently. I\'m sure
it can be done if the sheet software can handle hex. Mine doesn\'t.

It not only has to be a *valid* 48 bit hex value but it can\'t be
anything *more* (or less) than those 12 hex digits.

Additionally, depending on the table in which it resides, it might
need to be different from all other MACs present in that field
(for other entries) -- because no two devices have the same MAC.

This is trivial to guarantee with a DBMS. With a spreadsheet
(or untyped text), you rely entirely on the discipline of the person
entering the data (and we all know people are notorious for making
mistakes!)

DBMSs present so many richer ways of presenting and preserving
data to make the DBAs job easier.

What do you do when there are two entries in a spreadsheet that
obviously refer to the same thing?  E.g., a part number having
two different descriptions?  In a DBMS, you can ensure that
all part numbers are unique (trying to add another record with
an existing part number throws an error).   You can also encode
other criteria to safeguard the data going into the relation.
E.g., \"biological child\'s age must be less than age of parents\"
(duh!) or \"birthdate must be in the past\", etc.

Try some simple problems in a spreadsheet... like keeping track
of the songs in your music collection.  Then, try to convince
yourself that your spreadsheet is better than just a textual table!

Or, document your family tree for a couple of generations.

I keep my \"list of books\" as a database with several related tables. I\'m
tempted to migrate to an spreadsheet, because, for instance, I can thus carry
it in my phone.

I don\'t carry a phone; my library exists on a set of eReaders.

[I had 80 \"photocopier paper cartons\" (~1.5 cu ft... holds 10
500 sheet reams of A-size paper) of paperback novels when I
moved here. I\'ve scanned or replaced all of the dead trees
with epubs, over the years... a few *thousand* titles!]

And, instead of simplifying their contents to a flat \"list\",
I\'m more inclined to implement FTS as I can often remember the
name of a character -- or some plot device -- but seldom the
title of a book. So, accessing by title, author, publisher,
length, year of publication, etc. are largely useless to me
(for all but a select group of \"favorite\" titles).

This is doubly so for technical articles.

[Coffee table books are handled entirely differently... they are
*intended* to be physical items that folks can peruse leisurely]

 

[Simon S Aysdie]

On Saturday, April 1, 2023 at 10:50:23 PM UTC-7, Jan Panteltje wrote:

On a sunny day (Sat, 1 Apr 2023 19:55:36 -0700 (PDT)) it happened Simon S
Aysdie <gwh...@ti.com> wrote in
9a5cb22f-c985-45c7...@googlegroups.com>:
On Saturday, April 1, 2023 at 9:11:05 AM UTC-7, John Larkin wrote:
I\'m writing a program to create a CSV file that lists possible
resistor matrix values. I might hand it off to other people to use. I
don\'t use spreadsheets so don\'t know much about them.

I can do lines with numbers and strings and commas, but I\'d like the
spreadsheets to start with introductory comments. So, how does one
format comments into a csv file?

A CSV file isn\'t a spread spreadsheet. It is a text file. Put your introduc> >tory strings in separated by commas.
You can put something like a # to start a line/comment, if you want. Your i> >nterpreter needs to be written to understand it.

--------
Make a text file called text.csv with a text editor and then open it with e> >xcel.,,,\" \"
2A,,,2D
,,3C,\" \"
,4B,,\" \"
5A,,,5D
closing,,comment,\" \"
--------
Above, I am not sure if the\\t in between the \'\" will make it past gaggle gr=
oups. (I mean \"\\t\")

Hey, that TAB appears here as 8 spaces
Could be 4 spaces too, depends?

It was certainly a single tab in the source. But, for example, Excel (that made those) is a CSV interpreter, and there are others too. So while there may be some handling conventions, but I am not sure how rigid the rules are..

Ultimately one needs to understand the actual behavior of their preferred interpreter.

I am ambivalent about CSV. There are a lot of reader functions in near every language that are fairly efficient in reading them. Like, read data csvread([RowK RowJ ColK ColL]) or simile. I think they\'ll read it regardless if it has a .CSV extension. I am just experiencing our VnV test programmer saving data as CSV. It\'s okay. It could be worse. lolz

> Just using spaces should be OK too I think..

What happened was simply that Excel tacked those \"\\t\" on to the end after I wrote the file in Notepad++. It did not like \"nothing\" after the last comma on a row, so where there was nothing, it inserted it.

I was wondering what happens if you use European notition for numbers..

300,2 for 300.2 for example ;-)

I think insisting on bastard notation is just asking for unnecessary extra work and problems. Patch the data first. Maybe people who write numbers (that comma way) need a period separated values (PSV) format of their own.

> For config files for programs I write I use my own formats.

Oh yes. I generically use .DAT extension.

The R&S FSWP phase noise analyzer saves data natively in a .DAT file. It has all the metadata in there too, and multi-channel storage. It is not cryptic. It is easy to write one\'s own reader without ever looking at a manual.

If you want to display graphics..
Same for data.

And you can always parse stuff with grep and awk

No grok grep awk.

 

[Carlos E.R.]

On 2023-04-04 07:30, Don Y wrote:

On 4/3/2023 2:30 PM, Carlos E.R. wrote:
Not in a spreadsheet.  Unless you treat the spreadsheet as a text table
and all of the data as typeless.

In which case, why aren\'t you just using a word processor?  And, living
with the inevitable mistakes that will creep into your data?  E.g., l00
is not a number -- despite looking like one!

In a database (\"relation\") you can \"relate\" different tables to each
other.
So, in addition to 1:1 relationships (implicit in a spreadsheet), you
can
have 1:1, 1:n, n:m, n:1, etc. relationships, as dictated by the data.

Just write several lines.

So, you have to be able to embed a newline in the field -- or, some other
delimiter to separate list elements (that won\'t, itself, be present in
any of the elements).

And, the \"type\" of the field now needs to be \"list of _____\" (instead
of just \"_____\").

Or, you deal with simple text and hope anything that consumes the data
won\'t gag on an undiscovered error in the data (!)

Or just several rows.

And, it\'s commonplace to have a DBMS put constraints on data
in ways that spreadsheets can\'t/don\'t.  As well as having a wider
range of data types (how do you store a MAC in a spreadsheet?)

Infinite ways. As text, for example. As a huge number.

The reason you want \"typed\" fields is to reduce errors.
Is this a number: THIS
Is this a MAC:   HeLlOboysandgirls
Is this a float:  123.456.78,,90

A MAC is just a long hexadecimal number that is displayed differently.
I\'m sure it can be done if the sheet software can handle hex. Mine
doesn\'t.

It not only has to be a *valid* 48 bit hex value but it can\'t be
anything *more* (or less) than those 12 hex digits.

Just use a spreadsheet software that allows 12 hex digits, and have a
validation rule or macro.

No, I don\'t know of such software, but it is not an intrinsic
limitation, it can be done.

Maybe some spreadsheet software can be coaxed to display an integer as hex.

Additionally, depending on the table in which it resides, it might
need to be different from all other MACs present in that field
(for other entries) -- because no two devices have the same MAC.

Yes, they can. Just write the MAC you wish. Of course they will clash if
they see one another, but you can wrongly program them like that.

But you can have that validation in a macro.


If one \"has\" to use a spreadsheet, one will find a way to do things.

This is trivial to guarantee with a DBMS.  With a spreadsheet
(or untyped text), you rely entirely on the discipline of the person
entering the data (and we all know people are notorious for making
mistakes!)

DBMSs present so many richer ways of presenting and preserving
data to make the DBAs job easier.

What do you do when there are two entries in a spreadsheet that
obviously refer to the same thing?  E.g., a part number having
two different descriptions?  In a DBMS, you can ensure that
all part numbers are unique (trying to add another record with
an existing part number throws an error).   You can also encode
other criteria to safeguard the data going into the relation.
E.g., \"biological child\'s age must be less than age of parents\"
(duh!) or \"birthdate must be in the past\", etc.

Try some simple problems in a spreadsheet... like keeping track
of the songs in your music collection.  Then, try to convince
yourself that your spreadsheet is better than just a textual table!

Or, document your family tree for a couple of generations.

I keep my \"list of books\" as a database with several related tables.
I\'m tempted to migrate to an spreadsheet, because, for instance, I can
thus carry it in my phone.

I don\'t carry a phone; my library exists on a set of eReaders.

I need to carry my list of books when I go shopping. If I don\'t have a
phone, I print it. I need the list or I can buy a repeated tittle by
mistake.

Thus, I do have a phone. And it does have spreadsheet software.

[I had 80 \"photocopier paper cartons\" (~1.5 cu ft... holds 10
500 sheet reams of A-size paper) of paperback novels when I
moved here.  I\'ve scanned or replaced all of the dead trees
with epubs, over the years... a few *thousand* titles!]

And, instead of simplifying their contents to a flat \"list\",
I\'m more inclined to implement FTS as I can often remember the
name of a character -- or some plot device -- but seldom the
title of a book.  So, accessing by title, author, publisher,
length, year of publication, etc. are largely useless to me
(for all but a select group of \"favorite\" titles).

This is doubly so for technical articles.

[Coffee table books are handled entirely differently... they are
*intended* to be physical items that folks can peruse leisurely]

--
Cheers, Carlos.

 

[Lenny Raha]

https://sulthanmesinpaving.com/tag/mesin-cetak-batako-mejayan-madiun/
https://sulthanmesinpaving.com/tag/mesin-cetak-batako-mejayan-madiun/
https://sulthanmesinpaving.com/tag/mesin-paving-madiun/
https://sulthanmesinpaving.com/tag/madiun/

 

[Lenny Raha]

https://www.crunchbase.com/event/project-support-a45d

 

[Lenny Raha]

https://www.crunchbase.com/event/project-support-a45d

 

[Don Y]

On 4/4/2023 3:36 PM, Carlos E.R. wrote:

On 2023-04-04 07:30, Don Y wrote:
On 4/3/2023 2:30 PM, Carlos E.R. wrote:
Not in a spreadsheet.  Unless you treat the spreadsheet as a text table
and all of the data as typeless.

In which case, why aren\'t you just using a word processor?  And, living
with the inevitable mistakes that will creep into your data?  E.g., l00
is not a number -- despite looking like one!

In a database (\"relation\") you can \"relate\" different tables to each other.
So, in addition to 1:1 relationships (implicit in a spreadsheet), you can
have 1:1, 1:n, n:m, n:1, etc. relationships, as dictated by the data.

Just write several lines.

So, you have to be able to embed a newline in the field -- or, some other
delimiter to separate list elements (that won\'t, itself, be present in
any of the elements).

And, the \"type\" of the field now needs to be \"list of _____\" (instead
of just \"_____\").

Or, you deal with simple text and hope anything that consumes the data
won\'t gag on an undiscovered error in the data (!)

Or just several rows.

And, then add a mechanism to tell anyone (anyTHING) using the data
that \"these N rows are to be treated as one entity\"?

And, it\'s commonplace to have a DBMS put constraints on data
in ways that spreadsheets can\'t/don\'t.  As well as having a wider
range of data types (how do you store a MAC in a spreadsheet?)

Infinite ways. As text, for example. As a huge number.

The reason you want \"typed\" fields is to reduce errors.
Is this a number: THIS
Is this a MAC:   HeLlOboysandgirls
Is this a float:  123.456.78,,90

A MAC is just a long hexadecimal number that is displayed differently. I\'m
sure it can be done if the sheet software can handle hex. Mine doesn\'t.

It not only has to be a *valid* 48 bit hex value but it can\'t be
anything *more* (or less) than those 12 hex digits.

Just use a spreadsheet software that allows 12 hex digits, and have a
validation rule or macro.

No, I don\'t know of such software, but it is not an intrinsic limitation, it
can be done.

Maybe some spreadsheet software can be coaxed to display an integer as hex.

You can also use a sheet of paper, a pencil and a straight-edge...

Additionally, depending on the table in which it resides, it might
need to be different from all other MACs present in that field
(for other entries) -- because no two devices have the same MAC.

Yes, they can. Just write the MAC you wish. Of course they will clash if they
see one another, but you can wrongly program them like that.

But you can have that validation in a macro.
If one \"has\" to use a spreadsheet, one will find a way to do things.

All this just to *avoid* using a tool that already has these features
built in?

Was learning how to use an electronic spreadsheet THAT traumatic as to
turn you off on learning other design paradigms?

This is trivial to guarantee with a DBMS.  With a spreadsheet
(or untyped text), you rely entirely on the discipline of the person
entering the data (and we all know people are notorious for making
mistakes!)

DBMSs present so many richer ways of presenting and preserving
data to make the DBAs job easier.

What do you do when there are two entries in a spreadsheet that
obviously refer to the same thing?  E.g., a part number having
two different descriptions?  In a DBMS, you can ensure that
all part numbers are unique (trying to add another record with
an existing part number throws an error).   You can also encode
other criteria to safeguard the data going into the relation.
E.g., \"biological child\'s age must be less than age of parents\"
(duh!) or \"birthdate must be in the past\", etc.

Try some simple problems in a spreadsheet... like keeping track
of the songs in your music collection.  Then, try to convince
yourself that your spreadsheet is better than just a textual table!

Or, document your family tree for a couple of generations.

I keep my \"list of books\" as a database with several related tables. I\'m
tempted to migrate to an spreadsheet, because, for instance, I can thus
carry it in my phone.

I don\'t carry a phone; my library exists on a set of eReaders.

I need to carry my list of books when I go shopping. If I don\'t have a phone, I
print it. I need the list or I can buy a repeated tittle by mistake.

What\'s wrong with repeats? If it was good enough to attract your
attention a *second* time -- even if you remember that this is a
potential second copy -- then why not buy it, use that purchase
as motivation to read it, again, NOW, and donate the \"consumed\"
copy to the library, etc.?

Neither of us (SWMBO & I) have been in a bookstore in 3 decades
(we do go to the annual \"library book sale\", though). We do all
of our book shopping on-line; it\'s highly unlikely that I\'m going
to find a brick-and-mortar, here, that will have the titles in
which I\'m interested \"on the shelf\". Even the ones that *might*
be semi-mainstream.

My most recent purchases:
_Ologies and Isms_
_Mouth Sounds_
_Your Brain on Art_
_Mechanisms for Reliable Distributed Real-Time Operating Systems_
_Webster\'s Compact Rhyming Dictionary_
I likely wouldn\'t KNOW of these titles if my book shopping occurred
in brick-and-mortar bookstores! OTOH, if I stumble on a reference
to a title while doing research, then I can open another window in
a browser and buy a copy - without having to remember to keep an
eye open for it \"in my travels\".

[I don\'t read \"novels\" until the author has written EVERY title in
a particular \"series\"/collection; I\'m not keen on finishing a
\"volume\" and having to wait a year for the next in the series to
be available! So, I usually have several \"partial collections\"
queued up waiting for the remaining \"volumes\" to become available.
Then, binge-read an entire series (I read ~500pp/week)]

Thus, I do have a phone. And it does have spreadsheet software.

[I had 80 \"photocopier paper cartons\" (~1.5 cu ft... holds 10
500 sheet reams of A-size paper) of paperback novels when I
moved here.  I\'ve scanned or replaced all of the dead trees
with epubs, over the years... a few *thousand* titles!]

And, instead of simplifying their contents to a flat \"list\",
I\'m more inclined to implement FTS as I can often remember the
name of a character -- or some plot device -- but seldom the
title of a book.  So, accessing by title, author, publisher,
length, year of publication, etc. are largely useless to me
(for all but a select group of \"favorite\" titles).

This is doubly so for technical articles.

[Coffee table books are handled entirely differently... they are
*intended* to be physical items that folks can peruse leisurely]

 

[bud--]

On 4/3/2023 6:20 AM, Jasen Betts wrote:

On 2023-03-31, Sid 03 <sidwelle@gmail.com> wrote:

Yes, \"Yes wire sizes for amperage can vary all over the place.\" is exactly what I found.
I used the calculator that was linked and it shows that AWG 40 was suitable for 1 amp at 1 foot long ?
I thought the rule etched it stone was the #10 was used for 30 Amp, #12 for 20 Amps, and #14 for Amps, where does this standard come from ?

NFPA NEC

I agree NEC, but for 90 degree insulation power wiring the NEC rating is
40A for #10, 30A for #12 and 25A for #14 but the maximum current rating
they can be used at is what is above. The higher rating can be used for
derating like for ambient temp and number of wires in a conduit. Wire
rating depends on how the wire is used, like ambient (which I think
others have said). Connectors (like lugs) also have a temperature rating.

Rating for use in UL industrial control panels (1996) is #28 - 0.8A,
#26 - 1A, #24 - 2A, #22 - 3A, #20 - 5A, #18 - 7A, #16 - 10A, #14 -
20A, #12 - 25A, #10 - 40A.

And why can\'t I find a chart that follows the AWG down into the 2? AWG gauges ?

NEC doesn\'t allow LV on those sizes.

I was surprised #27 is in the NEC for flexible cords (tinsel wire -
Christmas tree lights?) at 0.5A. Must need a fused plug. Next larger
size is #20.

Years ago I had a shop class where the instructor stated that 18 AWG was good for 3 amps and another instructor stated that 18 AWG was good for 5 amps maximum.
I just thought it would be simple to find a chart that definitively shows the small AWG(s)

NEC for #18 flexible cord, 2 current carrying conductors (ground wire
doesn\'t count), the rating is 10A.

I think the general answer is - it depends.

Figure out how much energy you can afford to lose in the wires and choose a
size that does better