New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move functions from sage.matroids.bitset_tools to sage.misc #14668
Comments
This comment has been minimized.
This comment has been minimized.
Changed dependencies from 7477 to none |
comment:2
Just uploaded a patch adding functionality to bitset.pxi and tests to misc_c.pyx. I took the liberty to clean up some of the docstrings and trailing whitespace; I hope that's ok. |
Author: Rudi Pendavingh, Stefan van Zwam |
comment:4
Hellooooooooooooooo !! Just a couple of comments : I thought at first that your I personally think that risking this confusion is not worth saving a I also did not understand from its docstring what Anyway, have fuuuuuuuuuuuuuuuuuuuuuuuuuuuunnn !!! Nathann |
Bitset enhancements |
comment:5
Attachment: trac_14668_bitsets.patch.gz
|
comment:6
Oh right ! Good choice Nathann |
comment:7
Hello, I'm giving here some comments that could either be used to improve this patch or be considered for a future patch. With path #13352, I tried to speed-up the In fact, the Since GMP is optimized for most processors (and used for arbitrary length numbers in sage), it would be nice to use it here. But may be this is relevant for (Frozen)Bitset only? David. |
comment:8
Indeed. I wonder how much of a speedup it would be to move to mpz_t as the base format. That sounds interesting to look at. |
comment:9
It looks like polymake has a bitset C++ class based on mpz_t: http://modular.math.washington.edu/home/wstein/www/home/cswiercz/sage-4.6/spkg/build/polymake-2.2.p5/src/lib/PTL/include/Bitset.h |
comment:11
Sure, it's better to have a dedicated ticket for possibly moving to gmp. |
comment:12
Replying to @sagetrac-Stefan:
Agreed - no point to hangup #7477 on improvements to this. Get matroids working, then investigate speedups to bitsets. |
Reviewer: Volker Braun |
comment:13
I was hoping that somebody would have set this to positive review by now, come oooon. And no endless feature request on tickets that obviously improve what we have... can you reimplement all of bitsets using foo? Sure, great idea! :-P |
comment:14
Replying to @vbraun:
Yes, it has been more than 24 hours. I was about to cruise the documentation and code style, etc. But I'm late to the party again, apparently. ;-) |
Merged: sage-5.11.beta1 |
There are several bitset tools in the matroid code:
These should be moved into sage.misc.
apply trac_14668_bitsets.patch
Component: misc
Author: Rudi Pendavingh, Stefan van Zwam
Reviewer: Volker Braun
Merged: sage-5.11.beta1
Issue created by migration from https://trac.sagemath.org/ticket/14668
The text was updated successfully, but these errors were encountered: