I've been working on a PR (https://github.com/yt-project/yt/pull/2286) that converts yt's testing framework from nose to pytest. I believe that it's mostly ready to go, so I was writing to see what everyone's thoughts on this change are, if there is any feedback on my implementation, and if anyone would be willing to help review it, since there are quite a few changes. Thanks, and have a good weekend!
This message is a follow-up of a discussion from yt-users.
I was having problems understanding the operation of
camera.rotate() (and camera.yaw() which is just a
I took a look at the code again, no rotation
of any kind changes the camera.focus object, which again I
find counterintuitive. Focus appears to be set and used in e.g.
camera.__init__() but then never used later.
Thus, my idea would be to update camera.__repr__() to show
something more informative, such as camera.lens.origin
and/or possibly some information from camera.orientation, and
then explain somewhere in the docs what the difference between
that and camera.position is. It is important for me to be able
to determine what the camera is doing because I am plotting
text labels in the 3D volume and I want to move the text labels
while moving the camera. Of course, I'm sure other people
have reasons for wanting the camera properties as well.
Also, If there's a standard projective geometry reference
which has a description of these things in the same language as
the yt implementation somewhere I'd love to see it. I'm not
sure if modifications of the camera class are part of your
4.0 work or not...
Andrew W. Steiner
Joint Faculty Asst. Prof. at UTK/ORNL
It is my pleasure to announce that applications are now open for Python in Astronomy 2020, to be held 20 - 24 April 2020 at Trinity College, Dublin in Dublin, Ireland.
Though the application form will be open until 23:59 UTC on 6 January 2020, I encourage you to complete the form soon to make sure you don’t miss the deadline.
The application form is at: https://forms.gle/mtdm6QKENdY8Y1Ph9
More information about the conference, including links to past years, is available at: http://openastronomy.org/pyastro/2020/
Finally, a brief excerpt from the description of the conference:
In addition to sharing information about state-of-the art Python Astronomy packages, the workshop will focus on improving interoperability between astronomical Python packages, mentoring current open-source contributors, and developing educational materials for Python in Astronomy. The meeting is therefore not only aimed at current developers, but also educators and research group leaders who are interested in being involved in these efforts.
Participant selection will be made with the goal of enhancing the Python in Astronomy community and we encourage requests to attend from all career levels. Effort will also be made to select participants who have contributed meaningfully to the Python in Astronomy ecosystem via providing educational materials, documentation, and/or code contributions. This conference is neither intended to be an introduction to Python nor only for expert-level Python developers.
On behalf of the SOC: Monica Bobra (co-chair), Andrew Leonard (co-chair), Will Barnes, Clara Brasseur, Juan Luis Cano, Rebecca Lange, Sophie Murray
I wanted to share with you a job posting to work with us at the
University of Illinois. It’s available at:
The short description is that we’re looking to invest in the yt
infrastructure, and bring it more closely in line with the modern
pydata ecosystem. This would mean working to utilize and interoperate
with libraries like dask and xarray, and will include designing and
documenting software changes and infrastructure. Plus, it will also
involve working with libraries used throughout both the scientific
ecosystem and in industry in modern data science. And, you’ll get to
work with fun people in both yt community *and* the pydata community!
All the work will be open source and this project is committed to
contributing to the broader ecosystem *wherever* we can.
I hope you’ll consider either applying, or passing this along to
someone you know that might be interested. All of the information in
the job posting should be considered authoritative, rather than this
email. If you’ve got any questions (including about specifics of the
job, the application process, etc) please do reach out to the contact
person on the form!
The frontend for AMRVAC (http://amrvac.org/) was just merged, thanks to the
persistence of that frontend's authors. Both of them have been working with
us on github and the yt slack and have shown an interest in further
improving support and yt in general.
To empower that I'd like to nominate them as project members. We'll need
three other project members to reply with a +1. When that happens I'll add
them to the website and give them a commit bit.
What: yt user/developer workshop
Where: Edinburgh, UK
When: June 29 to July 3, 2020
I'm very pleased to announce that there will be a yt user/developer
workshop at the Higgs Centre for Theoretical Physics at University of
Edinburgh from June 29 to July 3, 2020. The workshop will begin with a
couple days of tutorials for new users and then transition into development
activities. This will be a good opportunity to meet and join the yt
community. More information to follow, but mark your calendars and diaries
now. I hope to see you next summer!
We used to have a weekly PR triage meeting, but then, we stopped
having one! I have re-created one, set up for 9:30AM Central time on
Fridays for the next couple weeks. They worked really well while we
did them. I've also left it be a bit long so that if there's any
non-PR-triage work we can or should do, we can do that too.
I know this isn't ideal for West Coast folks, but I'd be happy to set
up another one as well. Looking forward to seeing you! The
invitation is copied below, and there's a link to a URL that will add
it to your calendar. I'll try (but will likely forget) to send out
Matthew Turk is inviting you to a scheduled Zoom meeting.
Topic: yt PR triage and co-working
Time: Sep 20, 2019 09:30 AM Central Time (US and Canada)
Every week on Fri, until Nov 1, 2019, 7 occurrence(s)
Sep 20, 2019 09:30 AM
Sep 27, 2019 09:30 AM
Oct 4, 2019 09:30 AM
Oct 11, 2019 09:30 AM
Oct 18, 2019 09:30 AM
Oct 25, 2019 09:30 AM
Nov 1, 2019 09:30 AM
Please download and import the following iCalendar (.ics) files to
your calendar system.
Join Zoom Meeting
One tap mobile
+19292056099,,344730807# US (New York)
+16699006833,,344730807# US (San Jose)
Dial by your location
+1 929 205 6099 US (New York)
+1 669 900 6833 US (San Jose)
+1 647 558 0588 Canada
+49 30 3080 6188 Germany
+49 30 5679 5800 Germany
+49 69 7104 9922 Germany
+82 2 6105 4111 South Korea
+82 2 6022 2322 South Korea
+44 203 051 2874 United Kingdom
+44 203 481 5237 United Kingdom
+44 203 966 3809 United Kingdom
+44 131 460 1196 United Kingdom
+81 524 564 439 Japan
+81 3 4578 1488 Japan
+61 8 7150 1149 Australia
+61 2 8015 6011 Australia
+52 554 161 4288 Mexico
+52 229 910 0061 Mexico
Meeting ID: 344 730 807
Find your local number: https://zoom.us/u/abzljuNmCN
Join by SIP
Join by H.323
126.96.36.199 (US West)
188.8.131.52 (US East)
184.108.40.206 (Hong Kong)
Meeting ID: 344 730 807
Join by Skype for Business
As many of you know, the yt-project has been growing and evolving over the
past several years (to new domains, to new datasets, to support new
packages, etc.). To accompany that growth, we'd like to take the
opportunity to update our governance structure. We've been working on
updating our governance model for the yt project and I've submitted two
companion PRs with drafts of this updated governance:
Our existing governance structure is located at
The first PR is to a new governance repository, where our governance
documentation will live separately from the YTEPs. This will allow us to
maintain and minorly update our governance without having to update YTEP.
The second PR is to the YTEP repository and generally outlines the core
values and ideas we want our governance structure to reflect. Hopefully all
of the things I've listed in the YTEP are reflected in the governance docs.
As members of the community, I'd like to solicit feedback from all of you
about these governance documents. Do these reflect our community values?
Should we add anything? Do you feel everything is clear? Is this too much
governance for our community right now? Is there something that's missing?
Feel free to reply here or comment on the pull requests! Our governance
will be better with your feedback.
PS - I tried to build in a mentorship structure into our maintainer
structure to help with onboarding new maintainers. I'd especially like to
know if you all think this would be valuable to you or if it is adding
unnecessary constraints to our community.
I posted this as a comment on #2172, but I wanted to note it here.
Right now the holdup for merging yt-4 into master is the answer
testing. We actually would not expect the answers to be the same
between the two (at the very least because the ordering of values will
be different) so we need to do some kind of manually inspection.
My plan for addressing answer testing differences, which I will start
by doing manually:
* All grid and octree data should have either the same, or
justifiably different answers. In my view, "justifiably different"
includes unit changes, and also includes changes as a result of
particles being selected on edges of grid boundaries. These will be
documented. (See #2195 )
* Results for all data selections in SPH and particle datasets should
be identical in count and values, although the order will likely be
different. To address this, we will have a "sorting order" field that
is the morton index of the particles, and the values will be sorted
and compared. This should help to identify situations where different
numbers of particles are being selected (typically they should not be,
except for situations related to smoothing length.)
* Manual inspection of visualizations that avoid meshing in 4.0 and
that utilize meshing in 3.x.
I believe this should cover most of the cases, and will take to the
next step of verification. To conduct these tests, I'm going to work
on a script that outputs the appropriate values into an HDF5 file, and
then compare the results for both. This will be somewhat distinct from
the answer testing and designed for ease of exploration.
Once I have a system prepared for this, I will post back here, and I
will likely put the results online to view.