Re: Help-gnucap Digest, Vol 85, Issue 2

Thank you guys, I will try this on monday, it seem to work on my 
personal computer though !

Le 2012-10-20 18:00, [email protected] a écrit :
> Send Help-gnucap mailing list submissions to
> 	[email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.gnu.org/mailman/listinfo/help-gnucap
> or, via email, send a message with subject or body 'help' to
> 	[email protected]
>
> You can reach the person managing the list at
> 	[email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Help-gnucap digest..."
>
>
> Today's Topics:
>
>    1. Re: Output buffer size (al davis)
>    2. Re: Output buffer size (Felix Salfelder)
>
>
> 
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 19 Oct 2012 22:13:24 -0400
> From: al davis <[email protected]>
> To: [email protected]
> Subject: Re: [Help-gnucap] Output buffer size
> Message-ID: <[email protected]>
> Content-Type: Text/Plain;  charset="iso-8859-1"
>
> On Friday 19 October 2012, Romain GAILLETON wrote:
>> got an issue, when using huge amount of nodes the output of
>> gnucap is  formated like this
>>
>> v(1) .......................... v(n)\n\r
>> + v(n+1) ...................... v(m)
>>
>> by any change, would there be a way to change the output
>> buffer size to  avoid this sequence please ? "\r\n+ "
>
> option outwidth=_____
>
> The default value is 9999 (characters).  You have a lot of data
> there.  It might be a good idea to carefully select fewer
> probes.  In my experience, when the circuit is that big, I don't
> really want to look at all that.  It runs faster if you reduce
> the output data.
>
> Speaking of reducing the output data ......  If you are doing a
> transient analysis, specify "trace all" on the transient
> command, which prints all time steps including the hidden ones
> (which increases the data) then specify a huge step size, and
> let gnucap's automatic step control determine what is needed.
> Usually, you get all of better accuracy, faster run time, and
> smaller output data.
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 20 Oct 2012 09:04:08 +0200
> From: Felix Salfelder <[email protected]>
> To: [email protected]
> Subject: Re: [Help-gnucap] Output buffer size
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Oct 19, 2012 at 10:13:24PM -0400, al davis wrote:
>> On Friday 19 October 2012, Romain GAILLETON wrote:
>> > got an issue, when using huge amount of nodes the output of
>> > gnucap is  formated like this [..]
>>
>> option outwidth=_____
>>
>> The default value is 9999 (characters).  You have a lot of data
>> there.
>
> shouldnt outwidth better default to "no limit" (== 0?)? this looks 
> more
> natural: users like Romain who don't need it and probably autoprocess
> the output wouldnt run into it.
> i cant think of a use case of "random" newlines in the output right 
> now,
> but i guess it would involve changing the value anyway.
>
> YMMV
> felix
>
>
>
> ------------------------------
>
> _______________________________________________
> Help-gnucap mailing list
> [email protected]
> https://lists.gnu.org/mailman/listinfo/help-gnucap
>
>
> End of Help-gnucap Digest, Vol 85, Issue 2
> ******************************************


_______________________________________________
Help-gnucap mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/help-gnucap