All Projects → GuLinux → PlanetaryImager

GuLinux / PlanetaryImager

Licence: GPL-3.0 license
Qt capture software for astronomy, mainly planetary shooting

Programming Languages

C++
36643 projects - #6 most used programming language
c
50402 projects - #5 most used programming language
CMake
9771 projects
python
139335 projects - #7 most used programming language
C#
18002 projects
shell
77523 projects

Projects that are alternatives of or similar to PlanetaryImager

pymeeus
Library of astronomical algorithms in Python
Stars: ✭ 25 (-44.44%)
Mutual labels:  astronomy, planets
api-rest
API - The Solar System OpenData
Stars: ✭ 18 (-60%)
Mutual labels:  astronomy, planets
ephemeris-compute-de405
A command-line tool for producing tables of the positions of solar system objects over time.
Stars: ✭ 14 (-68.89%)
Mutual labels:  astronomy, planets
sherpa
Fit models to your data in Python with Sherpa.
Stars: ✭ 125 (+177.78%)
Mutual labels:  astronomy
spherical geometry
A Python package for handling spherical polygons that represent arbitrary regions of the sky
Stars: ✭ 45 (+0%)
Mutual labels:  astronomy
ccd-reduction-and-photometry-guide
Read the CCD guide here:
Stars: ✭ 55 (+22.22%)
Mutual labels:  astronomy
moon-cheeser
Moon Cheeser is an infinite runner where the player plays as a mouse gathering cheese pieces and avoiding craters and other astronomical objects, such as comets and planets, on a moon made of cheese.
Stars: ✭ 32 (-28.89%)
Mutual labels:  moon
NICERsoft
Analysis software for the NICER mission
Stars: ✭ 12 (-73.33%)
Mutual labels:  astronomy
TreeCorr
Code for efficiently computing 2-point and 3-point correlation functions. For documentation, go to
Stars: ✭ 85 (+88.89%)
Mutual labels:  astronomy
moon-cli
✨ Easily scaffold a Moon project
Stars: ✭ 27 (-40%)
Mutual labels:  moon
P4J
Periodic time series analysis tools based on information theory
Stars: ✭ 42 (-6.67%)
Mutual labels:  astronomy
bidscoin
BIDScoin converts your source-level neuroimaging data to BIDS
Stars: ✭ 75 (+66.67%)
Mutual labels:  imaging
unity-excavator
Physical simulations on Unity
Stars: ✭ 20 (-55.56%)
Mutual labels:  astronomy
hodlmoon
A command line tool for crytocurrency data. When moon?
Stars: ✭ 25 (-44.44%)
Mutual labels:  moon
heyoka
C++ library for ODE integration via Taylor's method and LLVM
Stars: ✭ 151 (+235.56%)
Mutual labels:  astronomy
OAD
Collection of tools and scripts useful to automate microscopy workflows in ZEN Blue using Python and Open Application Development tools and AI tools.
Stars: ✭ 90 (+100%)
Mutual labels:  imaging
pico-solar-system
No description or website provided.
Stars: ✭ 186 (+313.33%)
Mutual labels:  planets
rust-fitsio
FFI wrapper around cfitsio in Rust
Stars: ✭ 17 (-62.22%)
Mutual labels:  astronomy
TART
Transient Array Radio Telescope
Stars: ✭ 20 (-55.56%)
Mutual labels:  astronomy
cellfinder
Automated 3D cell detection and registration of whole-brain images
Stars: ✭ 122 (+171.11%)
Mutual labels:  imaging

PlanetaryImager

=================

Qt capture software for astronomy, mainly planetary shooting.

Useful Links

Last build status:

Supported Cameras

  • ZWO ASI Cameras
  • V4L2 (including DMK and Celestron Skyris)
  • QHY
  • FLIR/Point Grey via FlyCapture2 (all interfaces)
  • IIDC (including all FLIR/Point Grey FireWire and USB models)

Requirements

  • Qt version >= 5.5
  • A recent boost library version (tested with 1.55 and above).
  • c++14 compliant compiler (tested with gcc >= 5 and clang)
  • OpenCV
  • boost (libboost-all-dev)
  • fxload (to load firmware on QHY cameras)
  • ccfits
  • libdc1394 (for IIDC driver)
  • FlyCapture2 SDK (for FLIR/Point Grey cameras)

Compile Howto

These are generic instructions, and assume you're already familiar with building a package from sources. If not, please try binary releases first.

mkdir build
cd build
cmake .. -DCMAKE_INSTALL_PREFIX=/usr
make all && sudo make install

To enable a driver not enabled by default, add -DBUILD_DRIVER_xxxx=ON when calling cmake, where xxxx is the driver's name. Alternatively, one can also pass DEFAULT_ON as argument to add_driver() in driver's CMakeLists.txt file.

To run without installing, you must specify the drivers location as a parameter. E.g. when in build directory, use:

src/planetary_imager --drivers .

Please look at the main website for more information on compiling and developing PlanetaryImager.

Uninstall

If you installed PlanetaryImager from a precompiled package, just use your package manager to remove it.

If you installed PlanetaryImager from sources, just go to the source directory where you compiled it, and run the folowing:

cat install_manifest.txt  | while read file; do [[ -r $file ]] && ! [[ -d $file ]] && sudo rm -f $file; done

When compiling from sources, it is often advised to uninstall the previous version before installing the new one.

IIDC (libdc1394)

If you camera is not detected, you may need to use a newer version of libdc1394. In case of building the library on your own, the supported USB device ids are hard-coded in usb/control.c in usb_products[]. You can check your camera's VID/PID by calling lsusb, e.g. (for the Firefly MV camera):

...
Bus 002 Device 003: ID 1e10:2001 Point Grey Research, Inc.
...

FlyCapture2 (FLIR/Point Grey)

Installation of FlyCapture2 SDK is required (available from the FLIR website). On Windows, make sure to add the binaries directory to PATH (by default, C:\Program Files\Point Grey Research\FlyCapture2\bin64 or C:\Program Files (x86)\Point Grey Research\FlyCapture2\bin). On Linux, if your distribution does not use .deb package format (which is used by the SDK), simply unpack the packages manually. In any case, run the install script to create udev device rules.

When building from sources, make sure that the FC2_INCLUDE_DIR variable in src/drivers/flycapture2/CMakeLists.txt is set correctly.

Credits

Application Icon: Moon Mosaic by Marco Gulino. Toolbar/action icons: TWG Retina Display Icons, darkened and with a few customizations to add more actions. IIDC & FlyCapture2 drivers: Filip Szczerek (GreatAttractor).

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].