octave-dev — GNU Octave developers' list

Re: [OctDev] new release?

[Dirk E. <ed...@de...>]

On Sat, Jul 03, 2004 at 01:27:07PM -0400, Paul Kienzle wrote:
> Will it cause problems for you if the build succeeds even
> when it fails?  That is, if I put in the -k business so that
> people can ignore things that don't build on their architecture
> unless they really need them, it won't generate an exit
> status on Debian builds.

Well, I'd rather have it succeed in the first place for me. 

> On second thought, I can put in a make parameter such as:
> 	make STOP=1
> Use this if you want to build and stop at the first error.  If
> nobody disagrees, that's what I will do.  I'll skip the nice
> report of what doesn't build for now.

I think I can also make it fault tolerant at my level because debian/rules,
a makefile, can call 'make' as '-make' and even if your make failed, it
would continue.

But I think that would open a can of worms. We need to decide between you
and me what we think will build under Debian, and then just build it. On
i386 and all other ten or eleven arches, if possible.

Dirk

-- 
White House officials praised the performance of the controversial 
new Diebold electronic voting machines, which successfully tabulated 
final results from Florida before a single vote was cast.
          -- Andy Borowitz, http://borowitzreport.com, 29 June 2004

Re: [OctDev] new release?

[Paul K. <pki...@us...>]

Will it cause problems for you if the build succeeds even
when it fails?  That is, if I put in the -k business so that
people can ignore things that don't build on their architecture
unless they really need them, it won't generate an exit
status on Debian builds.

On second thought, I can put in a make parameter such as:
	make STOP=1
Use this if you want to build and stop at the first error.  If
nobody disagrees, that's what I will do.  I'll skip the nice
report of what doesn't build for now.

Paul Kienzle
pki...@us...

On Jul 3, 2004, at 10:29 AM, Dirk Eddelbuettel wrote:

>
> Hi all,
>
> On Mon, Jun 21, 2004 at 04:51:21PM +0200, David Bateman wrote:
>> Dapr?s Rafael Laboissiere <ra...@de...> (le 21/06/2004):
>>> Should we impose a freeze on the involved packages until they get all
>>> together into testing?
>>
>> Yes, please... :-)
>
> It looks like things moved according to plan and octave2.1 and 
> octave-forge
> are now in testing.
>
> So shall we release a new octave-forge tarball for Debian unstable 
> and/or
> the world at large?  I'm CCing to the the submitter and bug report of a
> recent BTS request for a fresher octave-forge.
>
> Dirk
>
> -- 
> White House officials praised the performance of the controversial
> new Diebold electronic voting machines, which successfully tabulated
> final results from Florida before a single vote was cast.
>           -- Andy Borowitz, http://borowitzreport.com, 29 June 2004
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> digital self defense, top technical experts, no vendor pitches,
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
>

Re: [OctDev] new release?

[Dirk E. <ed...@de...>]

Hi all,

On Mon, Jun 21, 2004 at 04:51:21PM +0200, David Bateman wrote:
> Dapr?s Rafael Laboissiere <ra...@de...> (le 21/06/2004):
> > Should we impose a freeze on the involved packages until they get all
> > together into testing?
> 
> Yes, please... :-)

It looks like things moved according to plan and octave2.1 and octave-forge
are now in testing.

So shall we release a new octave-forge tarball for Debian unstable and/or
the world at large?  I'm CCing to the the submitter and bug report of a
recent BTS request for a fresher octave-forge.

Dirk

-- 
White House officials praised the performance of the controversial 
new Diebold electronic voting machines, which successfully tabulated 
final results from Florida before a single vote was cast.
          -- Andy Borowitz, http://borowitzreport.com, 29 June 2004

[OctDev] octave-forge build

[Paul K. <pki...@us...>]

Octave-forge often has build problems.  For most
people, these problems don't matter.  I would like
an elegant way to build everything by default, but
instead of stopping on errors build everything that
can be built.

The point of this is to cut down on tech support
requests.  Since many functions are independent
of each other, whether a function is built only matters
if somebody wants to use it.  However, to avoid a
false sense of security, I want to list the functions that
couldn't be built and go on.

The best I can think of is to introduce -k at the top level
and have it propagate to the submakes:

$(SUBMAKEDIRS):
	-cd $@ && $(MAKE) -k $(MAKECMDGOALS)

Collecting the failed targets is trickier.  Maybe if
each significant target operation were something like:
	$(call log,<command>)
where log is defined something like:
	log = if !$(1); then echo $@ failed in `pwd` >> $(TOPDIR)/log

If it really doesn't make sense to build one function if another
doesn't exist  then an explicit dependency will stop the follow-on
functions from being built if they are not strictly required.

Is this a problem that needs to be solved?

Is this solution as simple as it could be, but no simpler?

Can anyone suggest an alternative?

Thanks,

Paul Kienzle
pki...@us...

Re: [OctDev] new release?

[Dirk E. <ed...@de...>]

On Wed, Jun 23, 2004 at 05:05:11PM +0000, pki...@co... wrote:
> I don't mind waiting.  Let me know when the next window is available.

Well, doing mental arithmetic in public is somewhat risky, but IIRC Steve
said eight days two days ago -- so we should be fine by the end of next
weeks, if all goes well.
 
> Is it possible to push something to the build machines without breaking
> the window so that the cycle time is lower?

No, not directly. Developers have access to accounts on different
architectire, but the build dependencies for complex packages tend to not be
fulfilled, so one needs to bug debian-admin. Doable but tedious.

I'd say let's wait a reasonable amount of time to let the current
octave-forge enter testing, and then start a new cycle. Nothing wrong with
releasing a handful of tarball over a couple of days or weeks to iron
everything out. It really does not have to be perfect at the first attempt.

Hoep this helps, Dirk

> 
> Paul Kienzle
> pki...@us...
> 
> 
> > Daprès Dirk Eddelbuettel <ed...@de...> (le 21/06/2004):
> > > On Mon, Jun 21, 2004 at 04:51:21PM +0200, David Bateman wrote:
> > > > Dapr?s Rafael Laboissiere <ra...@de...> (le 21/06/2004):
> > > > > Should we impose a freeze on the involved packages until they get all
> > > > > together into testing?
> > > > 
> > > > Yes, please... :-)
> > > 
> > > Before or after the tarball for octave-forge that spawned this discussion is
> > > added?
> > 
> > I can wait two times ten days to get it... So before I suppose. Unless one
> > of the other blocking packages just added something and we can slip something
> > in with further delays being implied...
> > 
> > Cheers
> > David
> > 
> > -- 
> > David Bateman                                Dav...@mo...
> > Motorola CRM                                 +33 1 69 35 48 04 (Ph) 
> > Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax) 
> > 91193 Gif-Sur-Yvette FRANCE
> > 
> > The information contained in this communication has been classified as: 
> > 
> > [x] General Business Information 
> > [ ] Motorola Internal Use Only 
> > [ ] Motorola Confidential Proprietary
> > 
> > 
> > -------------------------------------------------------
> > This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> > Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> > Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> > REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
> > _______________________________________________
> > Octave-dev mailing list
> > Oct...@li...
> > https://lists.sourceforge.net/lists/listinfo/octave-dev
> 

-- 
I think, honestly, we're practicing a new form of desperation. 
   -- Jon Stewart to Bill Moyers concerning 'The Daily Show'

Re: [OctDev] new release?

[<pki...@co...>]

I don't mind waiting.  Let me know when the next window is available.

Is it possible to push something to the build machines without breaking
the window so that the cycle time is lower?

Paul Kienzle
pki...@us...


> Daprès Dirk Eddelbuettel <ed...@de...> (le 21/06/2004):
> > On Mon, Jun 21, 2004 at 04:51:21PM +0200, David Bateman wrote:
> > > Dapr?s Rafael Laboissiere <ra...@de...> (le 21/06/2004):
> > > > Should we impose a freeze on the involved packages until they get all
> > > > together into testing?
> > > 
> > > Yes, please... :-)
> > 
> > Before or after the tarball for octave-forge that spawned this discussion is
> > added?
> 
> I can wait two times ten days to get it... So before I suppose. Unless one
> of the other blocking packages just added something and we can slip something
> in with further delays being implied...
> 
> Cheers
> David
> 
> -- 
> David Bateman                                Dav...@mo...
> Motorola CRM                                 +33 1 69 35 48 04 (Ph) 
> Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax) 
> 91193 Gif-Sur-Yvette FRANCE
> 
> The information contained in this communication has been classified as: 
> 
> [x] General Business Information 
> [ ] Motorola Internal Use Only 
> [ ] Motorola Confidential Proprietary
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: [OctDev] new release?

[Rafael L. <ra...@de...>]

* Steve Langasek <vo...@de...> [2004-06-21 11:33]:

> On Mon, Jun 21, 2004 at 04:47:23PM +0200, Rafael Laboissiere wrote:
> > The problem is that there are circular dependencies between the new hdf5
> > packages and lots of others (including octave2.1, octave-forge and
> > octave-plplot).  This can be seen at:
> 
> >     http://bjorn.haxx.se/debian/testing.pl?package=hdf5
> 
> > The only way to fix this dead-lock situation is by manually adding a hint to
> > the program that promotes packages from unstable to testing (britney).  The
> > hints can be seen at:
> 
> >     http://ftp-master.debian.org/testing/hints/
> 
> > One thing that complicates the situation is that the number of packages
> > involved is quite high and new versions are constantly uploaded to unstable.
> > Since the 10-days rule must be obeyed, the joint promotion of all packages
> > keep being delayed.
> 
> > Should we impose a freeze on the involved packages until they get all
> > together into testing?
> 
> I would appreciate this.  It's unfortunate to see that plplot has
> recently reset the clock on testing propagation for these packages; [...]

Mea culpa.

> [...] it looks like octave2.1 is very close to being ready, since it has
> been built on m68k and alpha and it's just a question of prodding the
> buildd admins into getting those packages uploaded.
> 
> Since the clock has been reset, I don't see any reason a new
> octave-forge upload should be a problem, if it's done soon; of course,
> if there are architecture-specific problems getting octave-forge ready,
> this does not hold true.  You might also consider using an upload
> priority of "medium" here, to help prevent delays, or else just hold off
> for 8 days before uploading.

The use of hold off is perhaps a good idea.  Here is the list of source
packages concerned by the eventual freeze (this message is being Cc:ed to
their maintainers):

    hdf5 (J. Mouette)
    mpb (J. Mouette)
    pytables (F. Alted)
    octave2.1 (D. Eddelbuetel)
    octave-forge (D. Eddelbuetel)
    plplot (R. Laboissiere)
    statdataml (R. Laboissiere)

I think that in seven days from now everything will be stabilized (plplot
already successfully built on all architectures), unless new versions of
octave2.1 and octave-forge are uploaded to unstable.

When establishing the hint, you will probably have to take care of the
following packages:

    octave-gpc (R. Laboissiere)
    octave-sp (D. Eddelbuetel)

which would be made uninstallable by the upgrade of hdf5.    

> Release assistant, not ftp-admin.  Please don't mistake me for someone
> with direct authority over the archive. :)

Okay, I will not blame you for ftp-admin problems anymore :-)

-- 
Rafael

Re: [OctDev] new release?

[Steve L. <vo...@de...>]

On Mon, Jun 21, 2004 at 04:47:23PM +0200, Rafael Laboissiere wrote:
> The problem is that there are circular dependencies between the new hdf5
> packages and lots of others (including octave2.1, octave-forge and
> octave-plplot).  This can be seen at:

>     http://bjorn.haxx.se/debian/testing.pl?package=3Dhdf5

> The only way to fix this dead-lock situation is by manually adding a hint=
 to
> the program that promotes packages from unstable to testing (britney).  T=
he
> hints can be seen at:

>     http://ftp-master.debian.org/testing/hints/

> One thing that complicates the situation is that the number of packages
> involved is quite high and new versions are constantly uploaded to unstab=
le.
> Since the 10-days rule must be obeyed, the joint promotion of all packages
> keep being delayed.

> Should we impose a freeze on the involved packages until they get all
> together into testing?

I would appreciate this.  It's unfortunate to see that plplot has
recently reset the clock on testing propagation for these packages; it
looks like octave2.1 is very close to being ready, since it has been
built on m68k and alpha and it's just a question of prodding the buildd
admins into getting those packages uploaded.

Since the clock has been reset, I don't see any reason a new
octave-forge upload should be a problem, if it's done soon; of course,
if there are architecture-specific problems getting octave-forge ready,
this does not hold true.  You might also consider using an upload
priority of "medium" here, to help prevent delays, or else just hold off
for 8 days before uploading.

> [ N.B.: Steve Langasek is one of the ftp-admins who is helping us with th=
is
>   issue.  Josselin Mouette is the maintainer of the Debian hdf5 packages.=
  I
>   am CC:ing this message to them.  ]

Release assistant, not ftp-admin.  Please don't mistake me for someone
with direct authority over the archive. :)

Cheers,
--=20
Steve Langasek
postmodern programmer

Re: [OctDev] new release?

[David B. <Dav...@mo...>]

Dapr=E8s Dirk Eddelbuettel <ed...@de...> (le 21/06/2004):
> On Mon, Jun 21, 2004 at 04:51:21PM +0200, David Bateman wrote:
> > Dapr?s Rafael Laboissiere <ra...@de...> (le 21/06/2004):
> > > Should we impose a freeze on the involved packages until they get a=
ll
> > > together into testing?
> >=20
> > Yes, please... :-)
>=20
> Before or after the tarball for octave-forge that spawned this discussi=
on is
> added?

I can wait two times ten days to get it... So before I suppose. Unless on=
e
of the other blocking packages just added something and we can slip somet=
hing
in with further delays being implied...

Cheers
David

--=20
David Bateman                                Dav...@mo...
Motorola CRM                                 +33 1 69 35 48 04 (Ph)=20
Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax)=20
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as:=20

[x] General Business Information=20
[ ] Motorola Internal Use Only=20
[ ] Motorola Confidential Proprietary

Re: [OctDev] new release?

[Dirk E. <ed...@de...>]

On Mon, Jun 21, 2004 at 04:51:21PM +0200, David Bateman wrote:
> Dapr?s Rafael Laboissiere <ra...@de...> (le 21/06/2004):
> > Should we impose a freeze on the involved packages until they get all
> > together into testing?
> 
> Yes, please... :-)

Before or after the tarball for octave-forge that spawned this discussion is
added?

Dirk

-- 
FEATURE:  VW Beetle license plate in California

Re: [OctDev] new release?

[David B. <Dav...@mo...>]

Dapr=E8s Rafael Laboissiere <ra...@de...> (le 21/06/2004):
> Should we impose a freeze on the involved packages until they get all
> together into testing?

Yes, please... :-)

D.

--=20
David Bateman                                Dav...@mo...
Motorola CRM                                 +33 1 69 35 48 04 (Ph)=20
Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax)=20
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as:=20

[x] General Business Information=20
[ ] Motorola Internal Use Only=20
[ ] Motorola Confidential Proprietary

Re: [OctDev] new release?

[Rafael L. <ra...@de...>]

* Dirk Eddelbuettel <ed...@de...> [2004-06-21 07:59]:

> On Mon, Jun 21, 2004 at 02:14:15PM +0200, David Bateman wrote:
> > 
> > Dirk,
> > 
> > It seems hdf5-1.6.2-3 is a valid candidate for debian testing, but is
> > stalled since it says it breaks octave, python, etc. Without this 
> > octave-forge can't migrate into testing. Does this mean that octave,
> > etc in testing need to be rebuilt against the new hdf5 library, so
> > it also can migrate to testing?
> 
> Possibly. I have no insights other than the (helpful) page 'why is package X
> not in testing' (at http://bjorn.haxx.se/debian/) says. 
> 
> Rafael is up to snuff on these things as octave influences his octave-*
> packages, incl. plplot.

The problem is that there are circular dependencies between the new hdf5
packages and lots of others (including octave2.1, octave-forge and
octave-plplot).  This can be seen at:

    http://bjorn.haxx.se/debian/testing.pl?package=hdf5

The only way to fix this dead-lock situation is by manually adding a hint to
the program that promotes packages from unstable to testing (britney).  The
hints can be seen at:

    http://ftp-master.debian.org/testing/hints/

One thing that complicates the situation is that the number of packages
involved is quite high and new versions are constantly uploaded to unstable.
Since the 10-days rule must be obeyed, the joint promotion of all packages
keep being delayed.

Should we impose a freeze on the involved packages until they get all
together into testing?
   
[ N.B.: Steve Langasek is one of the ftp-admins who is helping us with this
  issue.  Josselin Mouette is the maintainer of the Debian hdf5 packages.  I
  am CC:ing this message to them.  ]

-- 
Rafael

[OctDev] conv2

[Stefan v. d. W. <st...@su...>]

Hi all

conv2.oct implements a convolution directly, but the same convolution 
implemented in an M-file using the FFT is roughly 3 times as fast.  Is 
it done this way for any reason in particular?

Regards
Stéfan

Re: [OctDev] new release?

[Dirk E. <ed...@de...>]

On Mon, Jun 21, 2004 at 02:14:15PM +0200, David Bateman wrote:
> 
> Dirk,
> 
> It seems hdf5-1.6.2-3 is a valid candidate for debian testing, but is
> stalled since it says it breaks octave, python, etc. Without this 
> octave-forge can't migrate into testing. Does this mean that octave,
> etc in testing need to be rebuilt against the new hdf5 library, so
> it also can migrate to testing?

Possibly. I have no insights other than the (helpful) page 'why is package X
not in testing' (at http://bjorn.haxx.se/debian/) says. 

Rafael is up to snuff on these things as octave influences his octave-*
packages, incl. plplot.

Dirk

-- 
FEATURE:  VW Beetle license plate in California

Re: [OctDev] new release?

[David B. <Dav...@mo...>]

Dirk,

It seems hdf5-1.6.2-3 is a valid candidate for debian testing, but is
stalled since it says it breaks octave, python, etc. Without this=20
octave-forge can't migrate into testing. Does this mean that octave,
etc in testing need to be rebuilt against the new hdf5 library, so
it also can migrate to testing?

Regards
David

Dapr=E8s Dirk Eddelbuettel <ed...@de...> (le 21/06/2004):
> On Mon, Jun 21, 2004 at 07:19:43AM -0400, Paul Kienzle wrote:
> > In which case, we are ready for Dirk to build a new Debian
> > version, assuming he is not too busy at the moment.
>=20
> Sure, let me know where to grab a tarball from, or if I must, I'd attem=
pt a
> CVS checkout. =20
>=20
> This should fix three open Debian bugs
>=20
> 	http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=3Doctave-forge
>=20
> so a release is probably a good idea indeed.
>=20
> Dirk
>=20
> --=20
> FEATURE:  VW Beetle license plate in California
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKN=
D
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev

--=20
David Bateman                                Dav...@mo...
Motorola CRM                                 +33 1 69 35 48 04 (Ph)=20
Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax)=20
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as:=20

[x] General Business Information=20
[ ] Motorola Internal Use Only=20
[ ] Motorola Confidential Proprietary

Re: [OctDev] new release?

[Dirk E. <ed...@de...>]

On Mon, Jun 21, 2004 at 07:19:43AM -0400, Paul Kienzle wrote:
> In which case, we are ready for Dirk to build a new Debian
> version, assuming he is not too busy at the moment.

Sure, let me know where to grab a tarball from, or if I must, I'd attempt a
CVS checkout.  

This should fix three open Debian bugs

	http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=octave-forge

so a release is probably a good idea indeed.

Dirk

-- 
FEATURE:  VW Beetle license plate in California

Re: [OctDev] new release?

[David B. <Dav...@mo...>]

Dapr=E8s Paul Kienzle <pki...@us...> (le 21/06/2004):
> So are all the issues addressed that we are going to address?
>=20
> If I've been following correctly, the comm and fixed toolboxes
> are now ready.

I think the fixed point and cyclgen/cyclpoly bugs are fixed...

> Arguably there are still bugs in symbolic and sparse since
> neither use the new concatenation mechanism and neither
> use the new save mechanism that David put into place.

What new concatenation method? Do you mean "cat", in that
case it can be argued that neither does the galois or
fixed point types. In any case either if these are implemented
there is nothing to stop a user using "[]" and getting the
wrong result, so implementing these functions just gives a=20
false sense of security.... Still need to get "[]" fixed
within octave itself..

> And there is the issue of what to do about shadowed
> octave functions which I wrote about earlier.
>=20
> If no one volunteers, I'm content to leave this issues into the
> next release in order to get this release out now.  It will be
> a couple of weeks at least before I can get to it.

Which? The next release or this one :-)

Cheers
David

--=20
David Bateman                                Dav...@mo...
Motorola CRM                                 +33 1 69 35 48 04 (Ph)=20
Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax)=20
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as:=20

[x] General Business Information=20
[ ] Motorola Internal Use Only=20
[ ] Motorola Confidential Proprietary

Re: [OctDev] new release?

[Paul K. <pki...@us...>]

So are all the issues addressed that we are going to address?

If I've been following correctly, the comm and fixed toolboxes
are now ready.

Arguably there are still bugs in symbolic and sparse since
neither use the new concatenation mechanism and neither
use the new save mechanism that David put into place.

And there is the issue of what to do about shadowed
octave functions which I wrote about earlier.

If no one volunteers, I'm content to leave this issues into the
next release in order to get this release out now.  It will be
a couple of weeks at least before I can get to it.

In which case, we are ready for Dirk to build a new Debian
version, assuming he is not too busy at the moment.

Paul Kienzle
pki...@us...

Re: [OctDev] Re: [Octave-cvsupdate] octave-forge/main/fixed Array-f.cc,1.3,1.4

[Per P. <per...@ma...>]

On Jun 21, 2004, at 11:24, David Bateman wrote:
>  Changed it around...
>
> D.

OK, works fine now. Thanks!

/P

Re: [OctDev] Re: [Octave-cvsupdate] octave-forge/main/fixed Array-f.cc,1.3,1.4

[David B. <Dav...@mo...>]

Dapr=E8s Per Persson <per...@ma...> (le 21/06/2004):
> David,
> thanks for looking into this. There is one thing I don't understand:
>=20
> I need to place the instantiation (macros or not) within  #ifdef=20
> HAVE_ND_ARRAYS ...
> while you place it inside the opposite  #ifndef HAVE_ND_ARRAYS ...
>=20
> Things are still broken on OS X with the latest commit... :-(

You're right, again my fault.... Changed it around...

D.


>=20
> /Per
>=20
>=20
> On Jun 21, 2004, at 09:36, David Bateman wrote:
>=20
> >Update of /cvsroot/octave/octave-forge/main/fixed
> >In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv21496
> >
> >Modified Files:
> >	Array-f.cc
> >Log Message:
> >Use INSTANTIAT_ARRAY_CAT macro
> >
> >Index: Array-f.cc
> >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >RCS file: /cvsroot/octave/octave-forge/main/fixed/Array-f.cc,v
> >retrieving revision 1.3
> >retrieving revision 1.4
> >diff -u -d -r1.3 -r1.4
> >--- Array-f.cc	16 Jun 2004 11:22:20 -0000	1.3
> >+++ Array-f.cc	21 Jun 2004 07:36:52 -0000	1.4
> >@@ -71,11 +71,8 @@
> > template class MArray2<FixedPointComplex>;
> >
> > #ifndef HAVE_ND_ARRAYS
> >-template int cat_ra (Array<FixedPoint>& ra, const Array<FixedPoint>&=20
> >ra_arg,
> >-		     int dim, int idx, int move);
> >-template int cat_ra (Array<FixedPointComplex>& ra,
> >-		     const Array<FixedPointComplex>& ra_arg,
> >-		     int dim, int idx, int move);
> >+INSTANTIATE_ARRAY_CAT (FixedPoint);
> >+INSTANTIATE_ARRAY_CAT (FixedPointComplex);
> >
> > template int assign (Array2<FixedPoint>&, const Array2<FixedPoint>&);
> > template int assign (Array2<FixedPointComplex>&, const=20
> >Array2<FixedPoint>&);
> >
> >
> >
> >-------------------------------------------------------
> >This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> >Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> >Conference, June 28 - July 1 at the Moscone Center in San Francisco, C=
A
> >REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code=20
> >NWMGYKND
> >_______________________________________________
> >octave-cvsupdate mailing list
> >oct...@li...
> >https://lists.sourceforge.net/lists/listinfo/octave-cvsupdate
> >
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKN=
D
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev

--=20
David Bateman                                Dav...@mo...
Motorola CRM                                 +33 1 69 35 48 04 (Ph)=20
Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax)=20
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as:=20

[x] General Business Information=20
[ ] Motorola Internal Use Only=20
[ ] Motorola Confidential Proprietary

[OctDev] Re: [Octave-cvsupdate] octave-forge/main/fixed Array-f.cc,1.3,1.4

[Per P. <per...@ma...>]

David,
thanks for looking into this. There is one thing I don't understand:

I need to place the instantiation (macros or not) within  #ifdef 
HAVE_ND_ARRAYS ...
while you place it inside the opposite  #ifndef HAVE_ND_ARRAYS ...

Things are still broken on OS X with the latest commit... :-(

/Per


On Jun 21, 2004, at 09:36, David Bateman wrote:

> Update of /cvsroot/octave/octave-forge/main/fixed
> In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv21496
>
> Modified Files:
> 	Array-f.cc
> Log Message:
> Use INSTANTIAT_ARRAY_CAT macro
>
> Index: Array-f.cc
> ===================================================================
> RCS file: /cvsroot/octave/octave-forge/main/fixed/Array-f.cc,v
> retrieving revision 1.3
> retrieving revision 1.4
> diff -u -d -r1.3 -r1.4
> --- Array-f.cc	16 Jun 2004 11:22:20 -0000	1.3
> +++ Array-f.cc	21 Jun 2004 07:36:52 -0000	1.4
> @@ -71,11 +71,8 @@
>  template class MArray2<FixedPointComplex>;
>
>  #ifndef HAVE_ND_ARRAYS
> -template int cat_ra (Array<FixedPoint>& ra, const Array<FixedPoint>& 
> ra_arg,
> -		     int dim, int idx, int move);
> -template int cat_ra (Array<FixedPointComplex>& ra,
> -		     const Array<FixedPointComplex>& ra_arg,
> -		     int dim, int idx, int move);
> +INSTANTIATE_ARRAY_CAT (FixedPoint);
> +INSTANTIATE_ARRAY_CAT (FixedPointComplex);
>
>  template int assign (Array2<FixedPoint>&, const Array2<FixedPoint>&);
>  template int assign (Array2<FixedPointComplex>&, const 
> Array2<FixedPoint>&);
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code 
> NWMGYKND
> _______________________________________________
> octave-cvsupdate mailing list
> oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-cvsupdate
>

Re: [OctDev] new release?

[David B. <Dav...@mo...>]

Try the attached patch. It works for all of the test cases you propose he=
re.
Just a stupid little bug it seems.. This patch is applied to the CVS

Cheers
David

Dapr=E8s Quentin Spencer <qsp...@ie...> (le 18/06/2004):
> OK, I tested your changes to the coding stuff and this is what I found:
>=20
> bchpoly appears to give correct results for the cases I tested
> cyclgen(255,bchpoly(255,247)) gives the correct result
> cyclgen(255,bchpoly(255,239)) gives a matrix that is correct in the
> first 8x8 submatrix, and zeros everywhere else !?
> cyclpoly gives a vector containing all zeros for every input I tried.
>=20
> Well, I guess there's at least some progress since one case worked. I'm
> sorry the news isn't better.
>=20
> -Quentin
>=20
>=20
> David Bateman wrote:
>=20
> >According to Quentin Spencer <qsp...@ie...> (on 06/16/04):
> >=20
> >
> >>David,
> >>
> >>Thanks. The updates fixed hammgen. However, now I've found another bu=
g.=20
> >>I don't know if it was there all along or newly introduced. The=20
> >>following command should produce the 16x255 parity check matrix for a=
=20
> >>BCH 2-error correcting code:
> >>cyclgen(255,bchpoly(255,239))
> >>
> >>The result instead is:
> >>error: cyclgen: generator polynomial does not produce cyclic code
> >>
> >>I verified the resulting polynomial against MATLAB and they matched.
> >>  =20
> >>
> >
> >Ok, I'm a bit draft. The test I added checks if the polynomial is prim=
itive
> >rather than just irreducible. I'd previously tried to adapt this test =
in
> >the older code, but failed.
> >
> >So I went back to the basic implementation of dividing x^n-1 by the
> >polynomial and checking that there was no remainder. It appears to
> >work correctly for you test case now. Though maybe you want to give
> >it a bit more testing.. Changes checked into the CVS
> >
> >Regards
> >David
> >
> >=20
> >
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKN=
D
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev

--=20
David Bateman                                Dav...@mo...
Motorola CRM                                 +33 1 69 35 48 04 (Ph)=20
Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax)=20
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as:=20

[x] General Business Information=20
[ ] Motorola Internal Use Only=20
[ ] Motorola Confidential Proprietary

Re: [OctDev] Fixed still broken on OS X

[David B. <Dav...@mo...>]

I can't use the macro INSTATIATE_ARRAY_CAT as it only exists on the
most recent versions of octave. If I use it a 2.1.53 build will fail.
However, thinking about, as the template for cat_ra doesn't exist
either, I'm already in that case... Arrrggghhhh... Ok what is the
minimum build requirements for the next release of octave-forge?
2.1.50 and 2.1.57? If that is the case your fix is right.....

Cheers
David



According to Per Persson <per...@ma...> (on 06/19/04):
> David,
> fixed is still broken on OS X, I should have checked sooner but got 
> distracted.
> 
> On Jun 16, 2004, at 13:15, David Bateman wrote:
> 
> >You are right that they need to be instantiated. But cat_ra is an
> >NDArray thing and so should be in "#ifdef HAVE_ND_ARRAYS ... #endif".
>                                      ^^^^^^^^^^^^^^^^^^^^
> Right now the fix is conditioned on #ifndef HAVE_ND_ARRAYS ...
> How about the following patch?
> 
> /Per
> 
> 
> Index: Array-f.cc
> ===================================================================
> RCS file: /cvsroot/octave/octave-forge/main/fixed/Array-f.cc,v
> retrieving revision 1.3
> diff -u -d -b -w -r1.3 Array-f.cc
> --- Array-f.cc  16 Jun 2004 11:22:20 -0000      1.3
> +++ Array-f.cc  19 Jun 2004 14:35:48 -0000
> @@ -71,12 +71,6 @@
>  template class MArray2<FixedPointComplex>;
> 
>  #ifndef HAVE_ND_ARRAYS
> -template int cat_ra (Array<FixedPoint>& ra, const Array<FixedPoint>& 
> ra_arg,
> -                    int dim, int idx, int move);
> -template int cat_ra (Array<FixedPointComplex>& ra,
> -                    const Array<FixedPointComplex>& ra_arg,
> -                    int dim, int idx, int move);
> -
>  template int assign (Array2<FixedPoint>&, const Array2<FixedPoint>&);
>  template int assign (Array2<FixedPointComplex>&, const 
> Array2<FixedPoint>&);
>  template int assign (Array2<FixedPointComplex>&,
> @@ -99,6 +93,9 @@
>  #include <octave/MArrayN.h>
>  #include <octave/MArrayN.cc>
> 
> +INSTANTIATE_ARRAY_CAT (FixedPoint);
> +INSTANTIATE_ARRAY_CAT (FixedPointComplex);
> +
>  template class ArrayN<FixedPoint>;
>  template class MArrayN<FixedPoint>;
>  template class ArrayN<FixedPointComplex>;
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev

-- 
David Bateman                                Dav...@mo...
Motorola CRM                                 +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax) 
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary

Re: [OctDev] new release?

[David B. <Dav...@mo...>]

I believe it probably still works correctly for small values of n, since
that was all I tested previously. Oh, well it looks like the method I used
to create the generator matrix is too naive...

Cheers
David

According to Quentin Spencer <qsp...@ie...> (on 06/18/04):
> OK, I tested your changes to the coding stuff and this is what I found:
> 
> bchpoly appears to give correct results for the cases I tested
> cyclgen(255,bchpoly(255,247)) gives the correct result
> cyclgen(255,bchpoly(255,239)) gives a matrix that is correct in the
> first 8x8 submatrix, and zeros everywhere else !?
> cyclpoly gives a vector containing all zeros for every input I tried.
> 
> Well, I guess there's at least some progress since one case worked. I'm
> sorry the news isn't better.
> 
> -Quentin
> 
> 
> David Bateman wrote:
> 
> >According to Quentin Spencer <qsp...@ie...> (on 06/16/04):
> > 
> >
> >>David,
> >>
> >>Thanks. The updates fixed hammgen. However, now I've found another bug. 
> >>I don't know if it was there all along or newly introduced. The 
> >>following command should produce the 16x255 parity check matrix for a 
> >>BCH 2-error correcting code:
> >>cyclgen(255,bchpoly(255,239))
> >>
> >>The result instead is:
> >>error: cyclgen: generator polynomial does not produce cyclic code
> >>
> >>I verified the resulting polynomial against MATLAB and they matched.
> >>   
> >>
> >
> >Ok, I'm a bit draft. The test I added checks if the polynomial is primitive
> >rather than just irreducible. I'd previously tried to adapt this test in
> >the older code, but failed.
> >
> >So I went back to the basic implementation of dividing x^n-1 by the
> >polynomial and checking that there was no remainder. It appears to
> >work correctly for you test case now. Though maybe you want to give
> >it a bit more testing.. Changes checked into the CVS
> >
> >Regards
> >David
> >
> > 
> >
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev

-- 
David Bateman                                Dav...@mo...
Motorola CRM                                 +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax) 
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary

Re: [OctDev] Re: release notes

[Paul K. <pki...@us...>]

On Jun 19, 2004, at 12:33 PM, Paul Kienzle wrote:

> I would suggest configure.add script with lines such as:
> 	AC_SUBST(SHADOWED)
> 	OCTAVE_CHECK_EXIST(xxx,,[SHADOWED="$SHADOWED xxx"])

Oops ... a symbol is shadowed if exists in octave, so that should be:

	OCTAVE_CHECK_EXIST(xxx,[SHADOWED="$SHADOWED xxx"])

> Makeconf.add with:
> 	SHADOWED=@SHADOWED@
> and a Makefile which copies xxx.m.in to xxx.m if xxx is in
> $(SHADOWED) and removes xxx.m if it isn't. For oct-files,
> you need to build xxx.oct if xxx is in $(SHADOWED) or
> remove xxx.oct if it isn't.