I tried git init and pasting the GLFW directory containing glfw3.h file also but still these errors:

fatal: Not a git repository (or any of the parent directories): .git
make[1]: Entering directory `/home/igcl/Desktop/REBOUND_WINTER_2017/hannorein-rebound-ebf9357/src'
Compiling source file display.c ...
cc -c -std=c99 -Wpointer-arith -D_GNU_SOURCE -O3 -Wall -g -Wno-unknown-pragmas -fPIC -DL

Bug report

Bug summary

The example shown here:

https://yt-project.org/docs/dev/visualizing/plots.html#plots-of-2d-datasets

shows the classic windtunnel with a step test problem. In this problem, the l

Currently the LightCurveFile and LightCurve repr's are very similar and I wonder if this is causing/ will cause a little confusion for people.

I wonder if we should change the LightCurveFile repr to something like

![image](https://user-images.githubusercontent.com/14965634

For hydrostatic atmospheres, we have different approaches depending on the solver. These should be documented together with the test problems.

@gully How do you feel about adding your list of other data analysis packages (e.g. ranked by GitHub stars) as a page to the PyKE sphinx docs? The title of the page could be something like "Other packages", "See also" or "Third-party data analysis tools".

If we do this now, then Christina can include it in the screencast for her AAS splinter session talk. It would be good to flash it up in th

The python implementation of leapfrog does not make use of the fact that drifts can be combined when not storing output, causing it to be slower than necessary. Comparing to the C implementation, it also appears to not be as precise.

Writing an np.array of bool is silently ignored. Is this on purpose? It would be useful if at least a warning were returned.

TARDIS is not only compatible with Python 2.7
typo in recommend on installation
update the link to tardis_env3. yml

change the running tardis to tardis configuration file
move formal integral to configuration

move stella to helper scripts

It would be good to write a page in the docs where we talk about the Stingray-agnostic basics: how we observe the sky, what is a light curve, an introduction to periodograms, what are GTIs, etc.

When using Bridge and stopping conditions in one or more of the bridged systems, it is important to consider what happens when codes stop. Stopping conditions can cause a code to stop somewhere during its requested timestep, which would interfere with Bridge.
I am not sure how this is done properly at the moment.

E.g., what would be the correct way of handling the following:

system

Its clear that some of the conventions I've adopted for code and testing are unclear. For example:

• What is the different between an unmasked image, a 1D image and 2D image?

• Why does a tracer have images called blurred_profile_image_plane_images? How do these different from normal images? Model images?

• What does a 5x5 fixture mean?

Basically, the abstractions are good, but it need

The tutorial on The Effects of Interlaced Painting does not work. The function mesh.CompensateCIC no longer exists in the same place.

To reproduce, I installed nbodykit with pip3 install --user nbodykit on Debian. Then, copied the non-Jupyter code in the aforementioned tutorial into a text file, and run it on the comma

Show how to simulate a stream with a perturber.

List of small documentation improvements

Just comment to report a broken link, or suggest a documentation improvement! If it's a big make, consider filling a New Issue.

New contributors: you may want to pick one of these items and implement it. That's a good start! For that, it is recommended that you first open a [New Issue](https://githu

The problem: The code prints lots of info to standard out. Some users might want more or less info, or different info.

Suggested solution: Provide a flag for verbose or quite output. The default can be the existing setup, or whatever is deemed optimal.

This is a meta issue for tracking progress on issues related to the documentation.

Issues:

• #232 : Document setting hostebv from extinction law
• #207 : Document how to determine error in peak magnitude
• #204 : Document t0 definition in models
• #186 : More examples in documentation

Adstring outputs the wrong string when dec starts with negative zero (i.e. -0.5), while radec converts correctly.

>> adstring(15, -0.5)
" 01 00 00.0  +00 30 00"

>> radec(15, -0.5)
(1.0, 0.0, 0.0, -0.0, 30.0, 0.0)

The bug seems to be this line in adstring.jl:

dec_string = @sprintf("%+03.2d %02d %s", dec_deg, dec_min, dec_sec_string)

which ignores the negative zero.
A