I found the particular trace sequence that aborts the calling script.
Is this expected?
)r test-1.input
Notice that all goes well until line 15; where I try to reset the
"stats". Which happens.
But the following code (i.e. the reading of test-1.input is aborted.
Not even hidden; after the
Hi Kurt
As FriCAS exercise of the day, I tried to understand the source of your bug but
the best I can do is a minimal example (vaguely related to the original one)
and similar errors.
I do not know what mean "non extending category" and "has no ..." compilation
messages but there were
Hello Ric
Thanks for concerning yourself with this, it might be helpful indeed.
When slightly extending it's even worse ... strange ;)
I'd expect that u()$SI worked?
---
a) PhysicalUnit() : Category == SetCategory with -- inherit from SETCAT
b) baseUnits() == [x::% for x in
Indeed, installing TEXmacs 1.99.7 fixed the problems.
Thank you all for help
Slawomir
On Monday, July 16, 2018 at 3:59:28 AM UTC+2, oldk1331 wrote:
>
> Hi Slawomir,
>
> TeXmacs 1.0.7.18 was released 5 years ago, you should try more recent
> version, like 1.99.7.
>
--
You received this
Kurt Pagani wrote:
>
> Hello Ric
>
> Thanks for concerning yourself with this, it might be helpful indeed.
>
> When slightly extending it's even worse ... strange ;)
> I'd expect that u()$SI worked?
>
> ---
>
> a) PhysicalUnit() : Category == SetCategory with -- inherit from SETCAT
> b)
Martin R wrote:
>
> I am sorry it took so long. Attached there is a patch which appears to
> work well:
>
> (1) -> (3^2)$OUTFORM
>
> 2
>(1) 3
> Type:
> OutputForm
> (2) -> (3^2)$OUTFORM::INFORM
>
>(2) '(^ 3 2)
>
Foad S Farimani wrote:
>
> I was wondering if there are any plans/attempts to get GPU acceleration for
> numerical calculations on FriCAS? OpenCL would be the best API as it is
> cross platform and vendor natural.
There were some speculations but AFAIK no serious plans or attempts.
Note that
Bill Page wrote:
>
> On Sun, Jul 15, 2018 at 6:37 PM, Bill Page wrote:
> >
> > It seems that UNTRACE-2 was replaced by untrace2 in this commit
> >
> > https://github.com/fricas/fricas/commit/546108f1b65acadc38fc7d243b1b29770b6a770a
> >
> >
Raymond Rogers wrote:
>
> Found the call to UNTRACE-2
> Overall examining make.lst is pretty depressing. If nobody is going to
> fix (or explain) this then I will try another lisp.
Here you see "impedance mismatch". In Lisp undefined functions
and (global) variables are legal -- the
