Re: [Numpy-discussion] Migrating numpy Trac to github issues
On Mon, Jun 11, 2012 at 4:11 PM, Thouis (Ray) Jones tho...@gmail.comwrote: I've volunteered to help manage the migration of numpy tickets from Trac to github issues. Awesome, thanks! The first part of this process is to decide which tickets to migrate, and how to map Trac ticket data to github issue data. Question 1: Which tickets should be migrated? Open? Open and recently closed? All tickets? If Trac is going to disappear eventually and it's not too much trouble, all would be good. Question 2: Which parts of the tickets should be included, and in what way? For reference, these are the parts of a ticket (from http://trac.edgewall.org/wiki/TracTickets) Reporter Type (e.g., defect, enhancementt). Component Version Keywords Priority Milestone Assigned to/Owner Cc Resolution (fixed, invalid, wontfix, duplicate, worksforme, others?) Status (e.g., new, needs_review, etc.) Summary (brief description) Description (full description) Comments Attachments (not listed on the link above, but enabled for numpy Trac) ??? (Other) — I don't have access to the Trac configuration, so it's not clear if there are other fields I may be missing. As an initial suggestion, I propose: Reporter - yes, mapping Trac users to github users where possible. And if not possible, include username in comment on Github? Also, consider sending Trac users an email directly about the moved ticket? Type - yes, using github issues labels Component - yes, using labels Version - probably yes, using labels I don't find version useful at all, so I'd prefer to leave it out. Alternatively, keep as a comment on the issue. It's not important enough for a label. Also, because users can't assign labels, it will be extra work (which lands in comments) to attach this label to new issues after they're reported. Keywords - Yes, as a line in the github issue comments Priority - yes, using labels Milestone - yes, using github milestones Assigned to/Owner - yes, mapping to github users Cc - Yes, for github users we can map to, using @username Resolution - Only if tickets other than open are migrated, and as part of the issue comments Status - Yes, using labels Summary - Yes, as the github issue title Description - Yes, as the github issue body Comments - Yes, as github issue comments Attachments - Yes, linked in an issue comment All agreed. Note that the Trac database will be available for some time, and every migrated ticket will include a link to the original. If the Trac database is ever disabled, these links could be migrated to a static copy of the site. At some point, there may be a new location for ticket attachments, requiring changing links in some github issues. That's a separate issue from this discussion. Trac allows WikiFormatting, while github has a more limited markup language. As much translation as is possible will be performed within comments (code blocks, at an absolute minimum). In practice, code blocks are probably enough. Tickets will be migrated to a test repository before being moved to the numpy github repo, and there will be ample time to review the result before proceeding beyond that step. Sounds good. Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] numpy array in networkx graph?
can anyone give me a hint on the following code?
import network as nx
import pylab as plt
G=nx.Graph(M) # M is numpy matrix ,i.e:type(M)=numpy.ndarray
for i in xrange(len(M)):
tt=P[i,:].sum()
if tt==1:
G.add_node(i,color='blue')
elif tt==2:
G.add_node(i,color='red')
elif tt==3:
G.add_node(i,color='white')
else:
tt==4
G.add_node(i,color='green')
G.nodes(data=True)
T=nx.draw(G)
plt.axis('off')
plt.savefig(test.png)
I didn't get color change, still the defualt color is used.Did I miss
something?
my aim is to obtain:
something like:
find total number of w-red-red-z path
number of w-red-red-red-z path
number of w-red-red-red-red-z path
where w (left side of some cyclic polygon(can also be conjugated ring))
and z(right-side of it)are any of the colors except red.
any comment is appreciated?
Thanks
Bob
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] numpy array in networkx graph?
This seems to work:
import networkx as nx
import pylab
import numpy as N
M = N.random.random((10, 10))
G = nx.Graph(M)
node_colors = []
for i in xrange(len(M)):
if M[i,0] 0.5:
node_colors.append('white')
else:
node_colors.append('blue')
nx.draw(G, node_color=node_colors)
pylab.show()
~Brett
On Tue, Jun 12, 2012 at 1:49 PM, bob tnur bobtnu...@gmail.com wrote:
can anyone give me a hint on the following code?
import network as nx
import pylab as plt
G=nx.Graph(M) # M is numpy matrix ,i.e:type(M)=numpy.ndarray
for i in xrange(len(M)):
tt=P[i,:].sum()
if tt==1:
G.add_node(i,color='blue')
elif tt==2:
G.add_node(i,color='red')
elif tt==3:
G.add_node(i,color='white')
else:
tt==4
G.add_node(i,color='green')
G.nodes(data=True)
T=nx.draw(G)
plt.axis('off')
plt.savefig(test.png)
I didn't get color change, still the defualt color is used.Did I miss
something?
my aim is to obtain:
something like:
find total number of w-red-red-z path
number of w-red-red-red-z path
number of w-red-red-red-red-z path
where w (left side of some cyclic polygon(can also be conjugated ring))
and z(right-side of it)are any of the colors except red.
any comment is appreciated?
Thanks
Bob
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Enum/Factor NEP (now with code)
Hi all, It has been some time, but I do have an update regarding this proposed feature. I thought it would be helpful to flesh out some parts of a possible implementation to learn what can be spelled reasonably in NumPy. Mark Wiebe helped out greatly in navigating the NumPy code codebase. Here is a link to my branch with this code; https://github.com/bryevdv/numpy/tree/enum and the updated NEP: https://github.com/bryevdv/numpy/blob/enum/doc/neps/enum.rst Not everything in the NEP is implemented (integral levels and natural naming in particular) and some parts definitely need more fleshing out. However, things currently work basically as described in the NEP, and there is also a small set of tests that demonstrate current usage. A few things will crash python (astype especially). More tests are needed. I would appreciate as much feedback and discussion as you can provide! Thanks, Bryan Van de Ven ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] SciPy2012 conference: Last week for early birds, poster submissions
Hi everyone We're rapidly approaching SciPy2012 http://conference.scipy.org/scipy2012, which takes place in Austin, Texas from July 16th to 21st. This is a reminder that the *discounted early bird registration* closes on the 18th of this month. Also, we decided to keep the queue for *poster submissions* open until all slots are filled. So, whether you have a neat side project, a lightning talk gone rogue, or simply want to get the community talking about your latest and greatest idea--send in a poster abstract to 2012submissi...@scipy.org. See you in Austin! Stéfan ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
