Giter Club home page Giter Club logo

stellarsolver's People

Contributors

castorf avatar escribana avatar knro avatar lupinix avatar mattblack85 avatar mattiaverga avatar murveit avatar nouspiro avatar paolostivanin avatar rkaczorek avatar rlancaste avatar timsurber avatar vector-kerr avatar xsnrg avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

stellarsolver's Issues

Resource leak in astrometry/util/wcs-pv2sip.c

ct = fits_get_dupstring(hdr, "CTYPE1");
if ((ct && streq(ct, "RA---TPV")) || forcetan) {
// http://iraf.noao.edu/projects/ccdmosaic/tpv.html
logmsg("Replacing CTYPE1 = %s header with RA---TAN\n", ct);
fits_update_value(hdr, "CTYPE1", "RA---TAN");
}
ct = fits_get_dupstring(hdr, "CTYPE2");
if ((ct && streq(ct, "DEC--TPV")) || forcetan) {
logmsg("Replacing CTYPE2 = %s header with DEC--TAN\n", ct);
fits_update_value(hdr, "CTYPE2", "DEC--TAN");
}

ct is overwritten without being freed here.

Some C++ files built with C options

Example:

[ 22%] Building CXX object CMakeFiles/stellarsolver.dir/stellarsolver/sep/lutz.cpp.o
cc1plus: warning: command line option '-Wno-implicit-function-declaration' is valid for C/ObjC but not for C++

Resource leak in internalsextractorsolver.cpp

if (!pl_size(engine->indexes))
{
emit logOutput(QString("\n\n"
"---------------------------------------------------------------------\n"
"You must include at least one index file in the index file directories\n\n"
"See http://astrometry.net/use.html about how to get some index files.\n"
"---------------------------------------------------------------------\n"
"\n"));
return -1;
}

engine is lost here.

StellarSolverTester incorrectly checks available memory

On Raspberry Pi4 8GB StellarSolverTester issues the following message:

Evaluating Installed RAM for inParallel Option. Total Size of Index files: 31.7369 GB, Installed RAM: 1.71799e+10 GB
There should be enough RAM to load the indexes in parallel.

Of course, it hasn't got that memory available, and, in fact, on the Pi4 8GB, any one process still only has 4GB available to it.

Most options results in a out-of-memory errors and eventually a seg fault.

Similarly, latest build of kstars from Git either fail to solve, or crash kstars when using StellarSolver.

Update input image with solution WCS?

hi everyone,

Thanks for making this available! It is difficult to set up astrometry.net on mac.

I know that this is not the goal of the project, but it would be very useful if the solution WCS could be applied to the input image for processing data after the fact. I have not seen any way to do this for standalone images in kstars either, or am I missing something? thanks!

Resource leak in internalsextractorsolver.cpp

if (!pl_size(engine->indexes))
{
emit logOutput(QString("\n\n"
"---------------------------------------------------------------------\n"
"You must include at least one index file in the index file directories\n\n"
"See http://astrometry.net/use.html about how to get some index files.\n"
"---------------------------------------------------------------------\n"
"\n"));
return -1;
}

engine is lost here.

CLI example

Hi, first off all this work is what i've been looking for for a long time !
thanks a lot, it works like a charm and i'm sure it's the way things should be done

Could you provide a really basic command line example ?
For example
1- open fits file
2- SEP or Solve
3- ouput results

(yes : i'm lost in Qt cutties to understand your Tester)

Thanks again
Gilles

commandline version - solve-field script

Thank you very much for this amazing piece of software.
I was wondering if it was possible to setup a command-line version that would act as a direct (but more efficient) replacement for solve-field script from astrometry.net ?

Thank you very much for the help.

Run stellarsolver from terminal

options already set which works best for me. So I have a few questions for your program:

  1. Is it possible to run stellar solver from the terminal, without GUI because I want to put it in a docker, and run it automatically on every new image in a folder?
  2. If it is, how to set parameters (e.g. scale, initial position,...)?
  3. I need an output with the position of every star from the field and from the catalog, so I can calculate on-sky separation between these two points, and call it the precision of solving. Also, can I output the .wcs file with a solution?
  4. What about the distortion of a lens, how to check it, or set different tweak orders (astrometry.net option)?

These are all just a question I have because I am already using astrometry.net to solve all of it, but as I tried your software, it is much faster(under 2 sec, where astromety.net needs 4).

Build is not possible on Raspberry Pi 64 bit Bullseye

I get the following error when installing the prerequisites because I am asked to install obsolete software.

sudo apt -y install git cmake qt5-default libcfitsio-dev libgsl-dev wcslib-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package qt5-default is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'qt5-default' has no installation candidate
Paul

Get rid of more astrometry.net dependencies

Hi folks

This is not really a bug report, but more of a heads up :)
I actually did something very similar as you do here at:
https://github.com/mgreter/astrometrylib

I found your project a bit late in my attempt and since I IMHO got even a little bit
further at stripping down than you did here, I wanted to share some of my approaches.
Maybe you would like to take a peek at how I did the port ๐Ÿ˜‰

In the end I only have 65 files from astrometry.net left in my tree (stellarsolver around 400?).
I also got completely rid of an-qfits and the bl.h lists. The former was of course the hardest, since
that meant I would need a different loader for the indexes. Instead of reinventing that wheel in C again,
I decided it would be easier to just convert the indexes to a more (fixed) binary format. This has of
course the drawback that the original indexes are not directly compatible, but this really got rid of
a lot of the complicated dependencies. And the new binary index loader is only ~250 lines and it
IMO really makes sense to have them very easily readable for this purpose.

I also added multi-threading to my POC in order to check that possibility. Other than that pretty much everything
else is hardcoded in my POC yet, although at the right places to implement something useful instead.

Hope you don't mind me opening this github issue.

Looking forward to your feedback!

Resource leak in astrometry/util/fitstable.c

if (fitstable_read_row_data(intable, rows ? rows[i] : i, buf)) {
ERROR("Failed to read data from input table");
return -1;
}

buf is lost here.

if (offset + N > bl_size(tab->rows)) {
ERROR("Number of data items requested exceeds number of rows: offset %i, n %i, nrows %zu", offset, N, bl_size(tab->rows));
return -1;
}

dest and tempdata are lost here.

if (!tab->rows) {
ERROR("No data has been written to this fitstable");
return NULL;
}

fitsdata and cdata are lost here.

if (res) {
ERROR("Failed to read column from FITS file");
// MEMLEAK!
return NULL;
}

fitsdata and tempdata are lost here.

if (fseeko(table->fid, start + i * table->table->tab_w, SEEK_SET) ||
fits_write_data_array(table->fid, src, col->fitstype, col->arraysize, flip)) {
SYSERROR("Failed to write row %i of column %i", rowoffset+i, colnum);
return -1;
}

buf and src are lost here.

if (fitstable_write_header(outtable)) {
ERROR("Failed to write output table header");
return -1;
}
if (fitstable_copy_rows_data(intable, NULL, fitstable_nrows(intable), outtable)) {
ERROR("Failed to copy rows from input table to output");
return -1;
}

outtable is lost here.

SIGFPE on i386

Capturing a single frame in Focus:

Thread 22 "SextractorSolve" received signal SIGFPE, Arithmetic exception.
[Switching to Thread 0xa1d7fb40 (LWP 2531)]
0xb518c6db in InternalSextractorSolver::runSEPSextractor (this=0xae178e20)
    at /var/jenkins_home/workspace/kstars-ci_i386-stellarsolver/stellarsolver/internalsextractorsolver.cpp:252
252	/var/jenkins_home/workspace/kstars-ci_i386-stellarsolver/stellarsolver/internalsextractorsolver.cpp: No such file or directory.
(gdb) bt
#0  0xb518c6db in InternalSextractorSolver::runSEPSextractor() (this=0xae178e20)
    at /var/jenkins_home/workspace/kstars-ci_i386-stellarsolver/stellarsolver/internalsextractorsolver.cpp:252
#1  0xb518e63e in InternalSextractorSolver::extract() (this=0xae178e20)
    at /var/jenkins_home/workspace/kstars-ci_i386-stellarsolver/stellarsolver/internalsextractorsolver.cpp:99
#2  0xb518e63e in InternalSextractorSolver::run() (this=<optimized out>)
    at /var/jenkins_home/workspace/kstars-ci_i386-stellarsolver/stellarsolver/internalsextractorsolver.cpp:141
#3  0xb581fdcc in  () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#4  0xb52a43bd in start_thread (arg=0xa1d7fb40) at pthread_create.c:463
#5  0xb483bfe6 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108

This is an Atom i386 cpu with 1GB.

astrometry.log prints double values incorrectly on ARM 32bit

Whenever a double precision value is written to the log a crazy number is printed.
Affects users of Kstars on 32bit ARM like astroberry
It can be resolved by sprintf into a string followed by printf of the string but I imagine there is a compiler/linker option that might resolve it.
Not sure if it has any other flow on effect. Solving seems to work ok although I came across this helping another user whowas experiencing intermittent crashes when solving. The same values in the Kstars log look ok.
When astroberry is upgraded to 64 bit the issue should disappear.
I do recall a similar issue with the Avalon driver where printf of a double value requires the format to be %lf instead of %f to avoid a crash on RPi.
Google search shows a history of this issue or similar but no clear resolution and lots of red herrings.
I was able to reporduce the issue on Ubuntu 20.04 32 bit on RPi3 and with Ubuntu 20.04 64bit the log values print correctly
astrometrylog.txt

An issue with plate solve

Hello!
I have posted a message on EKOS forum on indilib.org describing my problems with plate solving. I am not sure if you (the authors) read the forum, so decided to create an issue here.

Basically, the problem is that while in many cases StellarSolver solves images just fine, there are cases where it fails and I do not see explanation.

Lets take the attached Rosette Nebula image, when I resolve the image it fails:

Automatically downsampling the image by 3
Evaluating Installed RAM for inParallel Option. Total Size of Index files: 1.96174 GB, Installed RAM: 62.7147 GB, Free RAM: 5.21823 GB
There should be enough RAM to load the indexes in parallel.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Sextractor with the 1-Default profile . . .
Stars Found before Filtering: 509
Stars Found after Filtering: 509
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Configuring StellarSolver
Scale range: 13.3125 to 16.2709 arcsec/pixel
Downsampling is multiplying the pixel scale by: 3
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Solver was aborted, timed out, or failed, so no solution was found
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Internal Extractor w/ StellarSolver failed after 591.048 second(s).
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Interestingly, when I un-check "Use Scale" (which by default is set to Low: 4.43751 and High: 5.42363) it gets solved immediately. I suspect that when I use KStars/EKOS to plate solve, it sets the Scale values and it is causing the issue, I have unchecked the scale options in EKOS settings but this does not make any difference:

image

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Automatically downsampling the image by 3
Evaluating Installed RAM for inParallel Option. Total Size of Index files: 1.96174 GB, Installed RAM: 62.7147 GB, Free RAM: 21.3926 GB
There should be enough RAM to load the indexes in parallel.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Sextractor with the 1-Default profile . . .
Stars Found before Filtering: 508
Stars Found after Filtering: 508
Starting 24 threads to solve on multiple scales
Solver # 1, Low 0.1, High 0.412326 arcsecperpix
Solver # 2, Low 0.412326, High 1.34931 arcsecperpix
Solver # 3, Low 1.34931, High 2.91094 arcsecperpix
Solver # 4, Low 2.91094, High 5.09722 arcsecperpix
Solver # 5, Low 5.09722, High 7.90816 arcsecperpix
Solver # 6, Low 7.90816, High 11.3438 arcsecperpix
Solver # 7, Low 11.3438, High 15.404 arcsecperpix
Solver # 8, Low 15.404, High 20.0889 arcsecperpix
Solver # 9, Low 20.0889, High 25.3984 arcsecperpix
Solver # 10, Low 25.3984, High 31.3326 arcsecperpix
Solver # 11, Low 31.3326, High 37.8915 arcsecperpix
Solver # 12, Low 37.8915, High 45.075 arcsecperpix
Solver # 13, Low 45.075, High 52.8832 arcsecperpix
Solver # 14, Low 52.8832, High 61.316 arcsecperpix
Solver # 15, Low 61.316, High 70.3734 arcsecperpix
Solver # 16, Low 70.3734, High 80.0556 arcsecperpix
Solver # 17, Low 80.0556, High 90.3623 arcsecperpix
Solver # 18, Low 90.3623, High 101.294 arcsecperpix
Solver # 19, Low 101.294, High 112.85 arcsecperpix
Solver # 20, Low 112.85, High 125.031 arcsecperpix
Solver # 21, Low 125.031, High 137.836 arcsecperpix
Solver # 22, Low 137.836, High 151.266 arcsecperpix
Solver # 23, Low 151.266, High 165.321 arcsecperpix
Solver # 24, Low 165.321, High 180 arcsecperpix
Scale range: 0.1 to 0.412326 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 0.218447 to 0.900713
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 15.404 to 20.0889 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 33.6495 to 43.8835
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 45.075 to 52.8832 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 98.4648 to 115.521
Scale range: 52.8832 to 61.316 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 115.521 to 133.943
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 112.85 to 125.031 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 246.517 to 273.125
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 101.294 to 112.85 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 221.273 to 246.517
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 25.3984 to 31.3326 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 55.482 to 68.4451
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 151.266 to 165.321 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 330.435 to 361.137
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 125.031 to 137.836 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 273.125 to 301.098
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 137.836 to 151.266 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 301.098 to 330.435
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 1.34931 to 2.91094 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 2.94751 to 6.35884
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 20.0889 to 25.3984 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 43.8835 to 55.482
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 61.316 to 70.3734 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 133.943 to 153.728
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 11.3438 to 15.404 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 24.78 to 33.6495
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 165.321 to 180 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 361.137 to 393.204
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 2.91094 to 5.09722 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 6.35884 to 11.1347
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 7.90816 to 11.3438 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 17.2751 to 24.78
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 5.09722 to 7.90816 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 11.1347 to 17.2751
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 37.8915 to 45.075 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 82.7727 to 98.4648
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 70.3734 to 80.0556 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 153.728 to 174.879
Scale range: 0.412326 to 1.34931 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 0.900713 to 2.94751
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 80.0556 to 90.3623 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 174.879 to 197.393
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 90.3623 to 101.294 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 197.393 to 221.273
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
Scale range: 31.3326 to 37.8915 degrees wide
Image width: 4944 pixels, Downsampled Image width: 1648 pixels; arcsec per pixel range: 68.4451 to 82.7727
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Internal StellarSolver Astrometry.net based Engine with the 1-Default profile. . .
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Solve Log Odds: 155.568
Number of Matches: 22
Solved with index: 4111
Field center: (RA,Dec) = (97.9495, 4.9492) deg.
Field center: (RA H:M:S, Dec D:M:S) = (06:31:47.870, +04:56:57.124).
Field is: (-14.7958, -9.18354) deg from search coords.
Field size: 3.05834 x 2.03064 degrees
Pixel Scale: 2.22755"
Field rotation angle: up is 78.6137 degrees E of N
Field parity: neg

You can find more test images (which fail and succeed), including the Rosetta one, here: https://drive.google.com/drive/folders/1S7Mn9SVHWSAEA8Cn5O0KCPFPdfGlnJaQ?usp=sharing

Rosetta_Light_300_secs_2020-12-04T23-27-54_001.zip

Resource leak in externalsextractorsolver.cpp

if(fits_create_tbl(new_fptr, BINARY_TBL, nrows, tfields,
ttype, tform, tunit, extfile, &status))
{
emit logOutput(QString("Could not create binary table."));
return status;
}

if(fits_write_col(new_fptr, TFLOAT, column, firstrow, firstelem, nrows, xArray, &status))
{
emit logOutput(QString("Could not write x pixels in binary table."));
return status;
}

xArray, magArray and yArray are lost here.

Resource leak in astrometry/util/fitsioutils.c

int fits_find_table_column(const char* fn, const char* colname, off_t* pstart, off_t* psize, int* pext) {
int i, nextens;
anqfits_t* fits;
fits = anqfits_open(fn);
if (!fits) {
ERROR("Failed to open file \"%s\"", fn);
return -1;
}
nextens = anqfits_n_ext(fits);
for (i=1; i<nextens; i++) {
const qfits_table* table;
int c;
table = anqfits_get_table_const(fits, i);
if (!table) {
ERROR("Couldn't read FITS table from file %s, extension %i.\n", fn, i);
continue;
}
c = fits_find_column(table, colname);
if (c == -1) {
continue;
}
if (anqfits_get_data_start_and_size(fits, i, pstart, psize)) {
ERROR("error getting start/size for ext %i in file %s.\n", i, fn);
return -1;
}
if (pext) *pext = i;
return 0;
}
debug("searched %i extensions in file %s but didn't find a table with a column \"%s\".\n",
nextens, fn, colname);
return -1;
}

fits is lost here (two returns).

Readme instructions to download and run stellar solver incorrect?

Hi,

I'm having trouble getting StellerSolver even running with MacOS. The readme.md says to get a recent dmg, but there appears to be none for StellarSolver in github... I guess this means KStars?

After using craft to install stellarsolver, there's no description on how to get it started or run it. Does it run from inside KStars or a different app? How do I get the gui I'm seeing in the readme to appear?

Sorry for the newb questions, but I've been hunting on how to do this for the weekend with no luck.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.