headers
Dan Stanger | 1 Jan 2003 17:46
Picon

Grobner basis routines

Here is some bargain basement grobner basis code.
It is derived from several sources, and may even be working;).
I would appreciate it if the list would look at it, run it thru some
tests, and give me comments.
Igrobner uses some improvments to reduce the computation.
Dan
Permalink | Reply | 2 comments |
headers
Stavros Macrakis | 2 Jan 2003 06:31
Picon

Bug database

Happy New Year to everyone!...

The bug database at sourceforge is getting pretty unwieldy.

It's getting to the point that when I run into a bug, it is not trivial
to check whether it's already been reported.  After all, there are >200
in the database (including both current and closed ones).  It would be
nice if we could categorize bugs somehow, or even do freetext search on
them.  Any ideas for this?  Should we introduce more categories?  For
example, we could categorize by subsystem: general simplifier (simp,
csimp), rational function package (ratXXX), taylor, limit, integrate,
rpart, etc.  Obviously users who don't look at the internals aren't
usually going to be able to correctly assign categories like this, but I
don't think many such users submit bug reports and maintainers can
always correct the category field later.  Or is there a better tool?

Also, I notice that no bugs have been declared Closed for over two
months.  Is that because bug-fixing is on hold while the new release is
being prepared?  Or because people are busy doing other things?  Or
because bugs are being fixed in source but not closed?  As I understand
it, our criterion for "closed" is that a fix has been put in source and
checked/tested by the person who applied it, right?  Do we do (or plan
to do) any sort of regression testing, making sure that previously
closed bugs don't reappear?

    Stavros
Permalink | Reply | 1 comment |
headers
Raymond Toy | 2 Jan 2003 15:20
Picon
Picon

Re: Bug database

>>>>> "Stavros" == Stavros Macrakis <stavros.macrakis <at> verizon.net> writes:

    Stavros> Happy New Year to everyone!...
    Stavros> The bug database at sourceforge is getting pretty unwieldy.

    Stavros> example, we could categorize by subsystem: general simplifier (simp,
    Stavros> csimp), rational function package (ratXXX), taylor, limit, integrate,
    Stavros> rpart, etc.  Obviously users who don't look at the internals aren't
    Stavros> usually going to be able to correctly assign categories like this, but I
    Stavros> don't think many such users submit bug reports and maintainers can
    Stavros> always correct the category field later.  Or is there a better tool?

This sounds like a good idea.

    Stavros> Also, I notice that no bugs have been declared Closed for over two
    Stavros> months.  Is that because bug-fixing is on hold while the new release is
    Stavros> being prepared?  Or because people are busy doing other things?  Or

I haven't looked at the bugs because I thought there was a code freeze
for the 5.9.0 release.  Perhaps there should have been a 5.9.0 branch
so work could have continued on the main branch?

Ray
Permalink | Reply | 0 comments |
headers
Dan Stanger | 2 Jan 2003 16:09
Picon

Issues

1) Is there a Code Freeze?  If so, on which mailing list was it stated,
and when
did the message go out, when does it start, and when does it end?
2) *.mk files?  It seems that the maxima.system and the *.mk files are
needed
to bootstrap and build the system, however if you just touch the *.mk
files,
then you can bootstrap and build without problem, then regenerate the
*.mk files.
Why have them at all?
Dan Stanger
Permalink | Reply | 5 comments |
headers
Raymond Toy | 2 Jan 2003 20:03
Picon
Picon

Re: Issues

>>>>> "Dan" == Dan Stanger <dan.stanger <at> ieee.org> writes:

    Dan> 1) Is there a Code Freeze?  If so, on which mailing list was it stated,
    Dan> and when did the message go out, when does it start, and when
    Dan> does it end?

Some digging in my mail archives shows that James Amundson sent a mail
on Oct 27 for rc2 asking developers not to make further commits.
Couldn't find anything more recent than that.  Since rc3 still hasn't
gone out, I assume the freeze still holds.

    Dan> 2) *.mk files?  It seems that the maxima.system and the *.mk
    Dan> files are needed to bootstrap and build the system, however
    Dan> if you just touch the *.mk files, then you can bootstrap and
    Dan> build without problem, then regenerate the *.mk files.  Why
    Dan> have them at all? 

I agree.  I think the top-level makefile should always just call the
appropriate lisp and run mk:oos to build them.  There's no need for
make to know that.  Then the *.mk files can go away completely (I
think).

Ray
Permalink | Reply | 4 comments |
headers
James Amundson | 2 Jan 2003 20:51
Favicon

Re: Issues

On Thu, 2003-01-02 at 13:03, Raymond Toy wrote:
> >>>>> "Dan" == Dan Stanger <dan.stanger <at> ieee.org> writes:
> 
>     Dan> 1) Is there a Code Freeze?  If so, on which mailing list was it stated,
>     Dan> and when did the message go out, when does it start, and when
>     Dan> does it end?
> 
> Some digging in my mail archives shows that James Amundson sent a mail
> on Oct 27 for rc2 asking developers not to make further commits.
> Couldn't find anything more recent than that.  Since rc3 still hasn't
> gone out, I assume the freeze still holds.

Disclaimers:

1) I am not pleased about the way the 5.9.0 release is going. It is
taking more than 10x as long to get from 5.9.0rc1 to 5.9.0 than I had
anticipated. Some of the reasons for the delay were avoidable, some were
unavoidable. (I'll analyze them on the list after the release is out.)

2) We will have a more formal plan for subsequent releases.

Answer:

Yes, there I announced a code freeze. No, I have not been strict about
enforcing it.

I have time to work in the remaining issues during the next few days. I
hope the remaining issues for release can be resolved during that time.
Based on past experience, I'm not making any promises.
(Continue reading)

Permalink | Reply | 3 comments |
headers
Jay Belanger | 2 Jan 2003 23:00
Favicon

maxima-mode


I've made some changes (fixes?) to maxima-mode; in particular there is
a new (improved?) indentation engine.  At any rate, it's been
rewritten so that it should be easy to fix any mistakes in it.
Also, preview-latex will preview EMaxima cells (in GNU Emacs), and
there is a command maxima-minibuffer, which take commands (and return
results) for Maxima in the minibuffer.  A copy is at
ftp://vh213601.truman.edu/pub/Maxima/Maxima-mode.tar.gz
(If there are no problems with it and no objections, I'll put it in
CVS after the freeze.)

Jay
Permalink | Reply | 0 comments |
headers
Jay Belanger | 2 Jan 2003 23:02
Favicon

Re: emaxima's problem with latex processing


Valerij Pipin <vpipin <at> irk.ru> writes:
> On Saturday 28 December 2002 20:19, Jesper Harder wrote:
...
> > Does this patch (untested) fix it?
> Yes! It works!
> Thanks a lot!

Yay Jesper!
Has this patch been put in CVS?

Jay
Permalink | Reply | 1 comment |
headers
Raymond Toy | 2 Jan 2003 23:38
Picon
Picon

Re: Issues

>>>>> "James" == James Amundson <amundson <at> fnal.gov> writes:

    James> I'm not quite sure what either of you have in mind. The *.mk files are
    James> unavoidable if you want (1) make to only rebuild an image if the source
    James> files have changed and (2) to have the list of source files determined
    James> solely by maxima.system. (I spent a couple of years of my professional

It seems to me that maxima.system contains the list of Lisp files
needed to build the entire system.  I was basically wondering why both
the *.mk and maxima.system files need to be maintained.  Could not the
*.mk files be created from maxima.system?

If so, could we not just always have make run mk:oos to build the
image?  If the sources files haven't changed, then nothing is done.
If they have, they'll get built anyway.

But perhaps I'm missing something....

Ray
Permalink | Reply | 2 comments |
headers
Jesper Harder | 2 Jan 2003 23:52
Picon
Picon
Picon

Re: emaxima's problem with latex processing

Jay Belanger <belanger <at> truman.edu> writes:

> Valerij Pipin <vpipin <at> irk.ru> writes:
>> On Saturday 28 December 2002 20:19, Jesper Harder wrote:
> ...
>> > Does this patch (untested) fix it?
>> Yes! It works!
>> Thanks a lot!
>
> Yay Jesper!
> Has this patch been put in CVS?

Yes and no.  It has been applied to `mactex.lisp' but not
`emaxima.lisp'.
Permalink | Reply | 0 comments |

Gmane