Can someone remind me why we need the strict and unstrict region
objects? The strict ones select by cell center, the unstrict by any
intersection. I seem to recall a concrete use case but I can't dredge
Additionally, if we are actually checking for periodicity, it seems to
me we have no need for non-periodic regions, right? We just coalesce
into a single rectangular prism object that, if appropriate for the
simulation, wraps around?
while vegging out in front of the TV, I've been playing with a pep8
checker (http://pypi.python.org/pypi/pep8), and I get the statistics
below for all the *.py files in yt. How much do we care about this
stuff? There are automatic tools
(http://pypi.python.org/pypi/autopep8/0.3) but I don't know if we can
trust them. Thoughts?
(the first column is the number of incidents)
70 E101 indentation contains mixed spaces and tabs
76 E111 indentation is not a multiple of four
605 E201 whitespace after '['
68 E202 whitespace before ')'
94 E203 whitespace before ','
105 E211 whitespace before '['
191 E221 multiple spaces before operator
57 E222 multiple spaces after operator
3769 E225 missing whitespace around operator
4271 E231 missing whitespace after ','
1080 E251 no spaces around keyword / parameter equals
986 E261 at least two spaces before inline comment
6 E262 inline comment should start with '# '
414 E301 expected 1 blank line, found 0
2061 E302 expected 2 blank lines, found 1
369 E303 too many blank lines (2)
168 E401 multiple imports on one line
4644 E501 line too long (80 characters)
1760 E701 multiple statements on one line (colon)
276 E702 multiple statements on one line (semicolon)
70 W191 indentation contains tabs
1585 W291 trailing whitespace
3 W292 no newline at end of file
3163 W293 blank line contains whitespace
221 W391 blank line at end of file
197 W601 .has_key() is deprecated, use 'in'
17 W602 deprecated form of raising exception
510.621.3687 (google voice)
What's the best way to handle boundary conditions? I was thinking
mainly, what's the smallest signal we can send -- typically into
Cython routines that might need to iterate -- that indicates, "wrap
this around the edge in this dimension"?
Essentially I think there are two main cases we need to consider for
the purposes of what yt wants, which are:
1) Periodic along an axis
2) Non-periodic (inflow, isolated) on an axis
This shows up for the plotting routines, vertex-centering of data, and
a handful of other things. I'm not sure how to handle this the best.
If we really have only these options (and I'm not a 100% on that) then
would it work to have a simple array of axes that hangs off the
hierarchy object, which is 0 for non-periodic on an axis and 1 for
Currently to verify file integrity with the install script we download
sidecar md5 file from yt-project.org. These aren't versioned, and md5
itself is largely deprecated for this.
I've created a new sha512-using version of the install script, which
uses sha512 hashes stored *in the install script* to verify file
integrity. This way any time these change we will be notified of
them. I'd like it if a few people could test this -- I have -- on
pristine systems. It changes both how the files are downloaded and it
now uses sha512sum, which should be available on most systems
(according to Kacper :).
You can do this by:
and then running it, but maybe supplying an alternate directory rather
than the default.
Thanks for any feedback.