myhdl-list — Mailing list for discussions on MyHDL

Re: [myhdl-list] installing myhdl stable and development package in parallel

[Thomas T. <tho...@de...>]

> Has somebody figured out a good way to install the stable version and 
> the code from the repository in parallel without the packages 
> interfering with each other?

I did the following. I am not sure, whether it really avoids intermixing
- but it should.

import sys
sys.path.insert(0,"path_to_myhdl_hg")
....

Re: [myhdl-list] installing myhdl stable and development package in parallel

[Christopher L. F. <pu...@gm...>]

> Are there any better ways of doing that?

I don't know if this is better or has the same issue but what I have  
been doing is similar, I cloned from the repository to something say  
myhdl_hg.

Then in the directory of my current myhdl WIP I create a soft link (ln  
-s) to myhdl_hg.  When I do an import myhdl it will grab from the  
local directory.  When I want to go back to the release version I  
remove the link.

You could also do this by removing the directory in site-packages and  
adding a soft link there.

Re: [myhdl-list] intbv.signed()

[Günter D. <dan...@we...>]

Jan Decaluwe wrote:
...
> 
> I would go for an integer to start with. That is what MyHDL does now for
> many operators. It is more efficient than constructing intbv's (although
> I dont' know how much more) and seems sufficient in many cases.

I was thinking about the processing of the signed() function and
basically need to do a categorization when the value of an intbv
instance is considered unsigned. In that case the the signed() function 
will change the value based on the msb bit, which is considered the sign 
bit. In the other case the value is considered signed and the function 
will return it just as is.

When considering intbv instances there are several combinations of
min/max values possible. The following diagram shows them:


     ----+----+----+----+----+----+----+----
        -3   -2   -1    0    1    2    3

1                     min  max
2                          min  max
3                min       max
4                min            max
5           min            max
6           min       max
7           min  max
8   neither min nor max is set
9   only max is set
10  only min is set


The horizontal line shows a number range from -3 to 3. Then each line 
shows different cases of min/max values of an intbv instance.

As an example, in the first case min=0 and max > 0. The second case min 
 > 0 and max > min, etc.

 From all those cases I think only two cases, namely 1 and 2, are where
the value is considered unsigned and the signed() function will return a
modified value.

In all other cases either there is no range specified or the min value
is < 0, which makes that intbv instance already considered signed and
the signed() function will just return the value as is.

So the test will be for min >= 0 and _nrbits > 0. That case will 
classify the intbv instance as unsigned and the signed() function will 
return the value as signed, with the sign being determined based on the 
msb. The msb is bit # _nrbits-1.

Note that case #10 (only min is set) could fulfill the requirement min 
 >=0, but as no max is set, _nrbits is 0 and hence the second test will 
not be True.

Guenter

[myhdl-list] installing myhdl stable and development package in parallel

[Günter D. <dan...@we...>]

Hello,

Has somebody figured out a good way to install the stable version and 
the code from the repository in parallel without the packages 
interfering with each other?

I did check out the mercurial code as myhdl_hg and then set the 
PYTHONPATH to it. My idea was to decide by the way of doing the import 
to take either of the packages. So instead of doing 'from myhdl' do 
'from myhdl_hg.myhdl'. Unfortunately there are imports inside the myhdl 
package that do the 'from myhdl' type import. So I end up mixing 
packages when doing the import from the repository.

Are there any better ways of doing that?

Cheers,

Guenter

[myhdl-list] Page about Contributing Patches

[Jan D. <ja...@ja...>]

As the subject is becoming more and more relevant, I
have written a page about Contributing Patches to
the MyHDL code:

http://myhdl.jandecaluwe.com/doku.php/dev:patches


-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
Kaboutermansstraat 97, B-3000 Leuven, Belgium
     From Python to silicon:
     http://myhdl.jandecaluwe.com

Re: [myhdl-list] intbv.signed()

[Jan D. <ja...@ja...>]

Günter Dannoritzer wrote:
> Hi,
> 
> I was gonna try out implementing the signed() function to intbv.
> 
> My first question is whether it should be a function or a property? What
> would be the decision about what to take. For example with the min and
> max values they are implemented as property. As there are no parameters
> needed, could the signed by also implemented as property?

To me, a property contains some static info about an existing object (even when
it is implemented as a method behind the curtains), while a method returns
some new object. So, it should be a method. The brackets indicate that
"something is being done".

> My next question is what signed() will return. Just the value as integer
> or will it be an intbv instance with the range set based on the _nrbits,
> but as +/- range?

I would go for an integer to start with. That is what MyHDL does now for
many operators. It is more efficient than constructing intbv's (although
I dont' know how much more) and seems sufficient in many cases. Note that
when we write:

a[:] = <some expression>

the range checking problem is transfered to the left-hand side.

Some other (more bit-oriented) operators return an unconstrained intbv
and we could do this also if there's a good reason. But I would
avoid trying to infer ranges.

Jan

-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
Kaboutermansstraat 97, B-3000 Leuven, Belgium
     From Python to silicon:
     http://myhdl.jandecaluwe.com

Re: [myhdl-list] _Waiter.diff [was: intbv.saturate, intbv.wrap]

[Jan D. <ja...@ja...>]

Christopher L.Felton wrote:

> When we have changes like this, do you want them emailed to you only or 
> copied to the mailing list as well?

I have written a page about how to contribute patches:

http://myhdl.jandecaluwe.com/doku.php/dev:patches

Please review it, it answers your questions and has some additional
relevant info.

Jan

-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
Kaboutermansstraat 97, B-3000 Leuven, Belgium
     From Python to silicon:
     http://myhdl.jandecaluwe.com

Re: [myhdl-list] intbv.signed()

[Günter D. <dan...@we...>]

Günter Dannoritzer wrote:

> 
> The slice by itself will return a new intbv with min=0, max=16, 
> _nrbits=4. From that I would think that the .signed() would change the 
> range to min=-4, max=4.

Just a quick correction, that should be min=-8, max=8.

[myhdl-list] intbv.signed()

[Günter D. <dan...@we...>]

Hi,

I was gonna try out implementing the signed() function to intbv.

My first question is whether it should be a function or a property? What
would be the decision about what to take. For example with the min and
max values they are implemented as property. As there are no parameters
needed, could the signed by also implemented as property?

My next question is what signed() will return. Just the value as integer
or will it be an intbv instance with the range set based on the _nrbits,
but as +/- range?

So for example if I do this:

a = intbv(0)[8:]
a[:] = 0x19

b = a[4:].signed()

The slice by itself will return a new intbv with min=0, max=16, 
_nrbits=4. From that I would think that the .signed() would change the 
range to min=-4, max=4.

 From the above example, the slice would return the value 0x9, which the 
signed() would converted to -7.

Am I considering that right?

Cheers,

Guenter

Re: [myhdl-list] _Waiter.diff [was: intbv.saturate, intbv.wrap]

[Christopher L. F. <cf...@uc...>]

>
>
>> This should be a benign change because the previous code simply  
>> tested
>> "if obj".  Again the numpy array errors in this test.  Explicitly
>> testing that obj is not None, "obj != None" prevented the error.
>
> ... though I think the idiomatic test should be 'obj is not None'.

Thanks for the hg information!  So I created another bundle that used  
the test "obj is not None" as you pointed out.  And includes the  
makefile.  Ran the tests again.

Re: [myhdl-list] _Waiter.diff [was: intbv.saturate, intbv.wrap]

[Christopher L. F. <cf...@uc...>]

>
>
>> This should be a benign change because the previous code simply  
>> tested
>> "if obj".  Again the numpy array errors in this test.  Explicitly
>> testing that obj is not None, "obj != None" prevented the error.
>
> ... though I think the idiomatic test should be 'obj is not None'.

Thanks for the hg information!  So I created another bundle that used  
the test "obj is not None" as you pointed out.  And includes the  
makefile.  Ran the tests again.

Re: [myhdl-list] _Waiter.diff [was: intbv.saturate, intbv.wrap]

[Jan D. <ja...@ja...>]

Christopher L. Felton wrote:
> I found another instance of the same/similar issue with the numpy array 
> while testing the latest change.  After the attached change and the 
> latest code from http://myhdl.sourceforge.net/hg/myhdl the code in 
> development ran without error.  Also all the test/core passed.

I believe you and have applied/pushed it.

> This should be a benign change because the previous code simply tested 
> "if obj".  Again the numpy array errors in this test.  Explicitly 
> testing that obj is not None, "obj != None" prevented the error.

... though I think the idiomatic test should be 'obj is not None'.

> I created (maybe?) one of those bundle things.  I don't quite have the 
> mercurial process down, I did a commit and wasn't able to diff after the 
> commit, which I guess make sense since there isn't no difference.

Of course, both commit and diff are local in your local repository.

All distributed revision control systems differ from centralized ones
in that they add a "second level" of commands. Some commands work
locally in your local repo's, some work between repo's. This is a
point that you'll have to understand in order to use it effectively.

 > But I
> wasn't sure what bundle did?  So I have a bundle before commit and 
> after. Figured it would take me a little longer to review the 
> documentation and didn't want to hold up the changes.

Look at it this way. After a (local) commit, you may want to publish
your changes, right?

To see the changes between your local repo and the parent repo:

hg out   # use the -vp option to review the patch

Now you would want to do:

hg push

to propagate your changes to the parent repo, just as you do
'hg pull' to download changes from the parent repo.

Except, this won't work for the myhdl repo at sourceforge. You can't
push to a http url, and moreover, I wouldn't let you :-)

Think of 'hg bundle' as an 'hg push' with me in the middle :-) It
does a similar thing, except that you have to send me the bundle file
and let me do the pull/push (after reviewing).

It's probably clear now why your pre-commit bundle didn't contain
any changesets, and why your post-commit bundle had the change
you described.

Jan

-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
Kaboutermansstraat 97, B-3000 Leuven, Belgium
     From Python to silicon:
     http://myhdl.jandecaluwe.com

Re: [myhdl-list] Adding new files

[Jan D. <ja...@ja...>]

Christopher L. Felton wrote:
> What is the best way to add new files in mercurial?  I added a simple 
> makefile for cver on OS X.  The file is attached, this was based on the 
> makefile.lnx should be straight forward.

hg add <yourfile>
hg commit

-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
Kaboutermansstraat 97, B-3000 Leuven, Belgium
     From Python to silicon:
     http://myhdl.jandecaluwe.com

[myhdl-list] Adding new files

[Christopher L. F. <cf...@uc...>]

What is the best way to add new files in mercurial?  I added a simple  
makefile for cver on OS X.  The file is attached, this was based on  
the makefile.lnx should be straight forward.

[myhdl-list] Adding new files

[Christopher L. F. <cf...@uc...>]

What is the best way to add new files in mercurial?  I added a simple  
makefile for cver on OS X.  The file is attached, this was based on  
the makefile.lnx should be straight forward.

Re: [myhdl-list] _Waiter.diff [was: intbv.saturate, intbv.wrap]

[Christopher L. F. <chr...@gm...>]

I found another instance of the same/similar issue with the numpy  
array while testing the latest change.  After the attached change and  
the latest code from http://myhdl.sourceforge.net/hg/myhdl the code in  
development ran without error.  Also all the test/core passed.

This should be a benign change because the previous code simply tested  
"if obj".  Again the numpy array errors in this test.  Explicitly  
testing that obj is not None, "obj != None" prevented the error.

I created (maybe?) one of those bundle things.  I don't quite have the  
mercurial process down, I did a commit and wasn't able to diff after  
the commit, which I guess make sense since there isn't no difference.   
But I wasn't sure what bundle did?  So I have a bundle before commit  
and after. Figured it would take me a little longer to review the  
documentation and didn't want to hold up the changes.

Re: [myhdl-list] Noob on the list

[Jan D. <ja...@ja...>]

Newell Jensen wrote:
> Hi all,
> 
> A little bit about me:
> I am new to the list but have been keeping a distant eye on myhdl for 
> some time.  I am currently a google summer of code participant working 
> for the gEDA project.  I am creating from scratch, a project manager 
> that incorporates all the different tools in the gEDA suite and puts 
> them in one place and also manages your project and all its files.  I am 
> using Python and PyGTK.
> 
> Jan, I saw that you are looking for a CMS for myhdl.org 
> <http://myhdl.org>.  I am actually currently in the process of creating 
> my own blog using Django and Byteflow.  Byteflow is a blog engine that 
> also shows up as a CMS on wikipediea.  I think it has everything that 
> you are looking for.

Mm, note that the competition is dokuwiki, as currently used on the
myhdl.jandecaluwe.com. I believe a wiki (plus access control) is closer
to our first needs than a blog.

On the subject, my current thinking about a "dream CMS" is as
follows:

- based on Django (or Turbogears or pylons): this gives us Python
and extensibility
- using restructured text as entry format instead of some wiki format:
then we can use a single format for all documentation
- using mercurial for revision control - as opposed to a wiki-specific
half-baked system.

And of course, the feature list should be as good as dokuwiki, which
is really not that bad.

Jan

-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
Kaboutermansstraat 97, B-3000 Leuven, Belgium
     From Python to silicon:
     http://myhdl.jandecaluwe.com

Re: [myhdl-list] _Waiter.diff [was: intbv.saturate, intbv.wrap]

[Jan D. <ja...@ja...>]

Christopher L. Felton wrote:

> I had not realized that this error was only for numpy arrays as the  
> example Thomas provided demonstrates.  I had originally thought this  
> would have failed for a list as well.  Is this an issue/error with the  
> numpy array?

I have applied and pushed Thomas' patch to the main repo, perhaps
you can try it and see if it works.

Jan

-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
Kaboutermansstraat 97, B-3000 Leuven, Belgium
     From Python to silicon:
     http://myhdl.jandecaluwe.com

Re: [myhdl-list] _Waiter.diff [was: intbv.saturate, intbv.wrap]

[Christopher L. F. <chr...@gm...>]

>
>> This would compare using '=='. Thomas has proposed to replace
>> this with 'is' test. I still don't really see what difference
>> this would make. Can you explain issue/error that you
>> are seeing?

> I proposed to remove the tuple because there is a problem with numpy
> comparison.
> This is a short test on the interactiv shell.
>
> ===============================================
>>>> a=[1,2]
>>>> b=[4,5]
>>>> a in b
>   = False
>>>> from numpy import arange
>>>> a = arange(3)
>>>> a in b
> ---------------------------------------------------------------------------
> ValueError                                Traceback (most recent  
> call last)
>
> ValueError: The truth value of an array with more than one element is
> ambiguous.
>  Use a.any() or a.all()
> =================================================

I had not realized that this error was only for numpy arrays as the  
example Thomas provided demonstrates.  I had originally thought this  
would have failed for a list as well.  Is this an issue/error with the  
numpy array?

Here is the snippet of code that I am using that fails.

  @instance
     def stimulus():
         """
         The following is a basic testbench to stimulate the CIC filter
         and create some plots.
         """

         yield clk.posedge
         rst.next = True
         yield delay(10)
         rst.next = False
         yield delay(10)

         for ii in range(Nloops):
             for jj in range(Nfft):
                 x.next = int(L * uniform(-1, 1))
                 xs[jj] = float(x)/L

                 ysave[jj] = float(y._val)/L  # Undo fix-point
                 yield clk.negedge

             favg = favg + abs(fft(ysave, Nfft)) / Nfft
             xfavg = xfavg + abs(fft(xs))/Nfft

         favg = favg / Nloops
         xfavg = xfavg / Nloops

Re: [myhdl-list] _Waiter.diff [was: intbv.saturate, intbv.wrap]

[Thomas T. <tho...@de...>]

> This would compare using '=='. Thomas has proposed to replace
> this with 'is' test. I still don't really see what difference
> this would make. Can you explain issue/error that you
> are seeing?

I proposed to remove the tuple because there is a problem with numpy 
comparison.
This is a short test on the interactiv shell.

===============================================
 >>> a=[1,2]
 >>> b=[4,5]
 >>> a in b
   = False
 >>> from numpy import arange
 >>> a = arange(3)
 >>> a in b
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)

ValueError: The truth value of an array with more than one element is 
ambiguous.
  Use a.any() or a.all()
=================================================

Re: [myhdl-list] _Waiter.diff [was: intbv.saturate, intbv.wrap]

[Jan D. <ja...@ja...>]

Christopher Felton wrote:
> Yes, the fix is needed for the added wiki page.  But I have not posted 
> the code that is dependent on the fix, yet.
> 
> Thanks for the procedure, sounds good and will do.  I am not familiar 
> (yet) with mercurial, I will acquaint myself with the tool.
> 
> Sounds like Thomas has taken care of this issue (diff, etc?).
> 
> I have seen this issue/error before as well, when the following 
> conditional is used in the code
> 
> in (posedge, negedge)

This would compare using '=='. Thomas has proposed to replace
this with 'is' test. I still don't really see what difference
this would make. Can you explain issue/error that you
are seeing?

Jan

-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
Kaboutermansstraat 97, B-3000 Leuven, Belgium
     From Python to silicon:
     http://myhdl.jandecaluwe.com

Re: [myhdl-list] _Waiter.diff [was: intbv.saturate, intbv.wrap]

[Christopher F. <cf...@uc...>]

Yes, the fix is needed for the added wiki page.  But I have not posted 
the code that is dependent on the fix, yet.

Thanks for the procedure, sounds good and will do.  I am not familiar 
(yet) with mercurial, I will acquaint myself with the tool.

Sounds like Thomas has taken care of this issue (diff, etc?).

I have seen this issue/error before as well, when the following 
conditional is used in the code

in (posedge, negedge)

  


On Mon, 21 Jul 2008 22:38:04 +0200
  Jan Decaluwe <ja...@ja...> wrote:
> Christopher L.Felton wrote:
>> Yes, definitely a more general approach was needed.  That looks like 
>>a  
>> good solution.
> 
> Is this patch needed for you new webpage to work? In that case it
> should probably be included in the codebase. The procedure that
> minimizes my work is as follows :-):
> 
> * describe shortly why the patch is needed, what it does
> * discuss shortly why it won't break forseeable things
> * as a minimum, run test/core to check nothing breaks
> * use mercurial to commit and use "hg bundle" to generate a
>   patch file to send me
> 
> The last step makes it really easy for me to apply and check
> the patch. Moreover, it preserves the patch author, so you
> get eternal credit for your work :-)
> 
> Jan
> 
> -- 
> Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
> Kaboutermansstraat 97, B-3000 Leuven, Belgium
>     From Python to silicon:
>     http://myhdl.jandecaluwe.com
> 
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's 
>challenge
> Build the coolest Linux based applications with Moblin SDK & win 
>great prizes
> Grand prize is a trip for two to an Open Source event anywhere in 
>the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> myhdl-list mailing list
> myh...@li...
> https://lists.sourceforge.net/lists/listinfo/myhdl-list

Re: [myhdl-list] _Waiter.diff [was: intbv.saturate, intbv.wrap]

[Jan D. <ja...@ja...>]

Christopher L.Felton wrote:
> Yes, definitely a more general approach was needed.  That looks like a  
> good solution.

Is this patch needed for you new webpage to work? In that case it
should probably be included in the codebase. The procedure that
minimizes my work is as follows :-):

* describe shortly why the patch is needed, what it does
* discuss shortly why it won't break forseeable things
* as a minimum, run test/core to check nothing breaks
* use mercurial to commit and use "hg bundle" to generate a
   patch file to send me

The last step makes it really easy for me to apply and check
the patch. Moreover, it preserves the patch author, so you
get eternal credit for your work :-)

Jan

-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
Kaboutermansstraat 97, B-3000 Leuven, Belgium
     From Python to silicon:
     http://myhdl.jandecaluwe.com

Re: [myhdl-list] intbv.saturate, intbv.wrap

[Jan D. <ja...@ja...>]

Christopher L.Felton wrote:
> I started (WIP) a wiki page for this, it is more convenient for  
> outlining code and displaying plots than the newsgroup, http://myhdl.jandecaluwe.com/doku.php/projects:gcicexample?do=backlink 

Thanks - I have added sidebar navigation for this. BTW, this
is done simply through a wiki page called 'sidebar' in a
certain namespace.

Jan

-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
Kaboutermansstraat 97, B-3000 Leuven, Belgium
     From Python to silicon:
     http://myhdl.jandecaluwe.com

Re: [myhdl-list] _Waiter.diff [was: intbv.saturate, intbv.wrap]

[Christopher L. F. <cf...@uc...>]

Yes, definitely a more general approach was needed.  That looks like a  
good solution.

On Jul 17, 2008, at 2:56 AM, Thomas Traber wrote:

> I just started to look at Christophers script.
>
> At first:
>
> Instead of
>
>> if not isinstance(obj, list) and not isinstance(obj, numpy.ndarray):
>
> in his _Waiter.diff, I would prefer the more general approach:
>
>> if not hasattr(obj,"__iter__"):
>
> In the hope that it is not too general.
>
>
>
>
>
>
>
>
> < 
> _Waiter 
> .diff 
> > 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
> myhdl-list mailing list
> myh...@li...
> https://lists.sourceforge.net/lists/listinfo/myhdl-list