On Sat, Apr 20, 2024 at 11:15:46AM +0800, Qian Yun wrote:
> Currently fricas-readline is not installed to ./target/*/bin/.
>
> I find it useful to debug with readline support:
>
> cd target/x86_64-linux-gnu
> FRICAS=. ./bin/fricas -rl
>
> Because readline's history feature is really
Currently fricas-readline is not installed to ./target/*/bin/.
I find it useful to debug with readline support:
cd target/x86_64-linux-gnu
FRICAS=. ./bin/fricas -rl
Because readline's history feature is really convenient when
you need to input the same things over and over again during
Also the calculation of rgb and print of "setrgbcolor"
should be made into a separate function, because the
2D PS output will need this as well.
- Qian
On 4/19/24 19:10, Qian Yun wrote:
I'd like to also include the following in this patch.
You will notice that the ps output has a strange gray
On Fri, Apr 19, 2024 at 09:02:59PM +0800, Qian Yun wrote:
>
>
> On 4/19/24 20:41, Waldek Hebisch wrote:
> >
> > Long ago I looked at communication protocol between various
> > processes that we use and my conclusion was that it is
> > inherently racy: there are parallel chanels of communication
On Fri, Apr 19, 2024 at 12:42:19AM -0700, 'Nasser M. Abbasi' via FriCAS -
computer algebra system wrote:
> FYI,
>
> This is update for the final summer 2024 edition of CAS integration tests
> about the issue Fricas giving zero for non zero integrand.
>
> There are 4 such cases found out of
On 4/19/24 20:41, Waldek Hebisch wrote:
Long ago I looked at communication protocol between various
processes that we use and my conclusion was that it is
inherently racy: there are parallel chanels of communication
and both ends assume that data comes in right order. I added
a little piece
On Fri, Apr 19, 2024 at 07:12:06PM +0800, Qian Yun wrote:
> You can notice a "pause" when you draw a picture like:
>
> (1) -> draw(x,x=1..2)
>Compiling function %C with type DoubleFloat -> DoubleFloat
>Graph data being transmitted to the viewport manager...
>FriCAS2D data being
On Sat, Apr 13, 2024 at 12:54:22PM +0200, Dima Pasechnik wrote:
>
> But that's what ECL is doing, compiling to C and then calling a C compiler?
> Would it be more useful to figure out why the resulting FriCAS runs
> considerably slower than the one built using SBCL ?
On social level it is
You can notice a "pause" when you draw a picture like:
(1) -> draw(x,x=1..2)
Compiling function %C with type DoubleFloat -> DoubleFloat
Graph data being transmitted to the viewport manager...
FriCAS2D data being transmitted to the viewport manager...
<<<>>>
(1)
I'd like to also include the following in this patch.
You will notice that the ps output has a strange gray background.
The following code snippet is responsible for setting color.
#define psShadeMax 17.0/* same as XShadeMax */
#define psShadeMul (1.0/(psShadeMax-1.0)) /* white
On Fri, Apr 19, 2024 at 01:26:27AM -0700, 'Martin R' via FriCAS - computer
algebra system wrote:
> I don't know how to do it. Note that this should really work with any lisp
> implementation to make sense, because some people (eg., me) will have
> fricas installed with sbcl (because this is
I don't know how to do it. Note that this should really work with any lisp
implementation to make sense, because some people (eg., me) will have
fricas installed with sbcl (because this is fastest), and the interface
shouldn't insist on an ECL installation.
Do you know how to do it?
Martin
FYI,
This is update for the final summer 2024 edition of CAS integration tests
about the issue Fricas giving zero for non zero integrand.
There are 4 such cases found out of 107,000 integrals.
Here they are
>sqlite3 cas_integration_tests.db
sqlite> select COUNT(*) from main where
13 matches
Mail list logo
