Re: gEDA-user: batch testing gschem features

2010-10-12 Thread Peter TB Brett
On Tue, 12 Oct 2010 09:58:16 +0400, Ineiev ine...@gmail.com wrote: Then I thought that the right script can be determined parsing the version string: echo (gschem-exit) quit.scm gschem_version=$(${GSCHEM} -s quit.scm 21 |grep version|sed s/.* //) and so on. this approach worked at least

Re: gEDA-user: pcb crooked traces

2010-10-12 Thread Armin Faltl
Andrew Poelstra wrote: Well, the C standard says that long must be ``at least'' 32 bits, maybe more. To the best of my knowledge, gcc uses a 32-bit long even on 64-bit systems, to maintain compatibility with old code. This was true last I checked, a year or two ago. Tested 5 minutes ago:

Re: gEDA-user: pcb crooked traces

2010-10-12 Thread Armin Faltl
DJ Delorie wrote: On Mon, 2010-10-11 at 15:25 -0700, Andrew Poelstra wrote: I think we want to allow negative locations. It would be nice to set parts outside of the pcb boundary, for example when initially placing everything. We limit ourselves to half so that *distances* can fit in

Re: gEDA-user: batch testing gschem features

2010-10-12 Thread Ineiev
On 10/12/10, Peter TB Brett pe...@peter-b.co.uk wrote: Why oh why doesn't gschem --version DTRT? Peter :-( Does it mean that a change like in the attachment has any chance in future gschem development? Cheers, Ineiev From 13ca491fba616a0cc0e8457d32d05529c4daa405 Mon Sep 17 00:00:00 2001 From:

gEDA-user: ngspice - simple lowpass simulation (newbie)

2010-10-12 Thread Fabio
Hello, I'd like to simulate a very simple circuit, an active lowpass filter. But I think I'm doing something wrong with my AOP, because ngspice cannot load the netlist: -- $ ngspice 78 - source ./spice.net Circuit: * gnetlist -g spice-sdb -o spice.net lowpass.sch Error on line 134 : u1 0 1

Re: gEDA-user: ngspice - simple lowpass simulation (newbie)

2010-10-12 Thread Fabio
Le 12 oct. 2010 à 17:12, John Doty a écrit : On Oct 12, 2010, at 8:36 AM, Fabio wrote: Error on line 134 : u1 0 1 vcc vss vout lf353/ns Unable to find definition of model vss - default assumed unknown parameter (vout) Dear John, If the component represents a subcircuit, SPICE

Re: gEDA-user: ngspice - simple lowpass simulation (newbie)

2010-10-12 Thread John Doty
On Oct 12, 2010, at 9:38 AM, Fabio wrote: Error on line 0 : e.xoa1.eos xoa1.7 0 POLY( 1 ) xoa1.16 xoa1.49 5e-3 1 Your ngspice lacks POLY() support. See http://www.brorson.com/gEDA/SPICE/x496.html for instructions on installing it. John Doty Noqsi Aerospace, Ltd.

Re: gEDA-user: ngspice - simple lowpass simulation (newbie)

2010-10-12 Thread John Doty
On Oct 12, 2010, at 9:38 AM, Fabio wrote: I'd be very grateful if someone could tell me what's the meaning of the error or send me a working example with an AOP. See http://www.gedasymbols.org/user/john_doty/models/opamp/index.html for some simple opamp models for use with gEDA. John Doty

Re: gEDA-user: pcb crooked traces

2010-10-12 Thread Rick Collins
At 11:26 AM 10/12/2010, you wrote: But if we limited everything to 2m, using unsigned integers, we'd be okay with 32 bits. I'm not sure what you're saying here. Having said that, I still want negative coordinates. So do we need to limit things to 1m? Yuck. He is saying that to avoid overflow

Re: gEDA-user: pcb crooked traces

2010-10-12 Thread Steven Michalske
Internally the origin of the grid should go to the middle of the board, but have the board translate the coords to physical of the upper left, or even lower left. Make some folks happy about their y decreasing or somthing or another. This removes the loss from the other three quadrents of area

Re: gEDA-user: pcb crooked traces

2010-10-12 Thread Armin Faltl
Andrew Poelstra wrote: When using signed integers for coordinates and offsets (vectors), by restricting to the positive quadrant, allowing a 2x2m board will still yield a 32-bit overflow, if you try to place a large footprint at the right edge of the board. So I think forbidding negative board

Re: gEDA-user: pcb crooked traces

2010-10-12 Thread Stefan Salewski
On Tue, 2010-10-12 at 11:44 -0400, Rick Collins wrote: WHOA!!! We should actually measure how much the application would For x86 architecture you may read http://en.wikipedia.org/wiki/X86 http://en.wikipedia.org/wiki/X86-64 it mentions MMX and similar, which made fast 64 bit integer

Re: gEDA-user: pcb crooked traces

2010-10-12 Thread Andrew Poelstra
On Wed, Oct 13, 2010 at 12:33:26AM +0800, Steven Michalske wrote: Internally the origin of the grid should go to the middle of the board, but have the board translate the coords to physical of the upper left, or even lower left. Make some folks happy about their y decreasing or somthing or

Re: gEDA-user: pcb crooked traces

2010-10-12 Thread Stefan Salewski
On Wed, 2010-10-13 at 00:48 +0800, Steven Michalske wrote: We should have NO base unit internally, and only scale to internal units on import, export, open, and save. OK, but we have snap to grid, and grid will have units, and display of coordinates. And arbitrary scale for output makes not

Re: gEDA-user: pcb crooked traces

2010-10-12 Thread Rick Collins
At 12:46 PM 10/12/2010, you wrote: On Tue, 2010-10-12 at 11:44 -0400, Rick Collins wrote: WHOA!!! We should actually measure how much the application would For x86 architecture you may read http://en.wikipedia.org/wiki/X86 http://en.wikipedia.org/wiki/X86-64 it mentions MMX and similar,

Re: gEDA-user: ngspice - simple lowpass simulation (newbie)

2010-10-12 Thread Fabio
Your ngspice lacks POLY() support. See http://www.brorson.com/gEDA/SPICE/x496.html for instructions on installing it. Yay, that was it ! Thanks a lot ! The plot in ngspice is now ok. For anyone using port, you just need to modify the Port file in the ports/release/science directory. Add

Re: gEDA-user: pcb crooked traces

2010-10-12 Thread Armin Faltl
Steven Michalske wrote: Internally the origin of the grid should go to the middle of the board, but have the board translate the coords to physical of the upper left, or even lower left. Make some folks happy about their y decreasing or somthing or another. Occasionally someone is changing

Re: gEDA-user: pcb crooked traces

2010-10-12 Thread Karl Hammar
John Doty: On Oct 10, 2010, at 5:38 AM, Karl Hammar wrote: On the downside for integers we have, if I may cite John Doty: There are subtle problems with carrying real number analytic geometry into a discrete domain. So far I have not found any good reasons for using integers, and John

Re: gEDA-user: pcb crooked traces

2010-10-12 Thread Peter Clifton
On Wed, 2010-10-13 at 00:05 +0200, Karl Hammar wrote: Why does #include stdio.h int main(void) { char cc = 0xc4 // 'ä' in latin1 short str = cc; printf(0x%04hx\n, str); } print 0xffc4 instead of 0x00c4 ? It is because 0xc4 is inserted into a char, not an unsigned char, and is in

Re: gEDA-user: pcb crooked traces

2010-10-12 Thread Karl Hammar
Peter Clifton: On Wed, 2010-10-13 at 00:05 +0200, Karl Hammar wrote: Why does #include stdio.h int main(void) { char cc = 0xc4 // 'ä' in latin1 short str = cc; printf(0x%04hx\n, str); } print 0xffc4 instead of 0x00c4 ? It is because 0xc4 is inserted into a char, not

Re: gEDA-user: pcb crooked traces

2010-10-12 Thread Andrew Poelstra
On Wed, Oct 13, 2010 at 12:59:42AM +0200, Karl Hammar wrote: Peter Clifton: The compiler will (correctly) sign-extend the assigned value in str when performing the type conversion. Close, but you missed to point out that a char is signed on my box. It could as well be unsigned, but