Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - FlyingBeagles

Pages: [1] 2
1
General / Re: ***SOLVED*** Directory Error Message - iMac
« on: 2018 July 27 01:08:32 »
Agreed and more a mistake on my part.

Appreciate the input Mike, my thanks

Pete

2
General / Re: ***SOLVED*** Directory Error Message - iMac
« on: 2018 July 26 21:19:03 »
Absolutely on the money Mike. 

Just curious that all others in that directory opened no probs. 

3
General / ***SOLVED*** Directory Error Message - iMac
« on: 2018 July 26 21:09:22 »
Hi All,

After changing the name of a directory on my iMac, Pixinsight can 'see' the files (double clicking the workspace etc) but won't load them.  The error I get is:
eading 4 image(s):
/Users/astromac/Pictures/Astrophotography Work/20180727 Tarantula Nebula New Process /MASTER_LIGHT_Blue_Cped_PS.xisf
<* failed *>
*** PixInsight API Error: MetaFileFormat: XISF: Invalid or nonexistent directory: /Users/astromac/Pictures/Astrophotography Work/20180727 Tarantula Nebula New Process /MASTER_LIGHT_Blue_Cped_PS.xisf
/Users/astromac/Pictures/Astrophotography Work/20180727 Tarantula Nebula New Process /MASTER_LIGHT_Green_Cped_PS.xisf
<* failed *>
*** PixInsight API Error: MetaFileFormat: XISF: Invalid or nonexistent directory: /Users/astromac/Pictures/Astrophotography Work/20180727 Tarantula Nebula New Process /MASTER_LIGHT_Green_Cped_PS.xisf
/Users/astromac/Pictures/Astrophotography Work/20180727 Tarantula Nebula New Process /MASTER_LIGHT_Lum_Cped_PS.xisf
<* failed *>
*** PixInsight API Error: MetaFileFormat: XISF: Invalid or nonexistent directory: /Users/astromac/Pictures/Astrophotography Work/20180727 Tarantula Nebula New Process /MASTER_LIGHT_Lum_Cped_PS.xisf
/Users/astromac/Pictures/Astrophotography Work/20180727 Tarantula Nebula New Process /MASTER_LIGHT_Red_Cped_PS.xisf
<* failed *>
*** PixInsight API Error: MetaFileFormat: XISF: Invalid or nonexistent directory: /Users/astromac/Pictures/Astrophotography Work/20180727 Tarantula Nebula New Process /MASTER_LIGHT_Red_Cped_PS.xisf

Worked fine before renaming the directory.  I have similar directories for other work and can access with no issues and I can open any other file in that directory, just not those masters.

Thoughts as to what might be causing this?

Pete

***Solved***. There was a space at the end of the directory that Pixinsight did not like.  That said, interesting how it could open other files in that directory, just not those four.   

4
Fingers crossed this is so Juan; I suspect you're right or MacOS might go the way of OS/2 :)

6
General / Re: Image (not star) alignment question
« on: 2018 July 23 17:54:02 »
***SOLVED***

In the end, it was my Oiii Subs that were the culprit.  I was using a version of Geoff's suggestion below (I was doing steps 1, 2 and 3 but instead of closing minimised and then did step 4). 

Using Geoff's steps, I carefully checked each crop against the "master cropped image" and they all aligned bar my Oiii.  So I went back to basics and did a dynamic star alignment on the Oili series against the master ref image (rather than relying on the automated process). 

It worked - when I applied the saved dynamic crop instance, it now aligns with the master cropped image so all good.

The Oiii subs were over two nights one at 300 and one at 600 seconds.

Thanks for your help Geoff, it confirmed I wasn't far off the mark and got me on the right track.

Pete

7
General / Re: Image (not star) alignment question
« on: 2018 July 23 04:47:24 »
Thanks Geoff,

Yep, initial images are the same size.  Will let you know how it goes.

Pete

8
General / ***SOLVED*** Image (not star) alignment question.
« on: 2018 July 23 03:07:46 »
Hi All,

Have recently gone through the process of registering and stacking a series of LRGB and HSO images taken over a few nights.  No probs, the images stack well.  The process for registering was using one great LUM image as my reference in image registration for all the series (this worked much better than registering in batches based on filter).

My question (for which I am certain there will be a ridiculously easy answer) is when cropping, I use DynamicCrop to size based off my 'worst' image edges but the resultant images do not then align (if that makes sense).  So for example, if I crop the LUM and Ha using the new instance feature, the stars are out of whack from each other.  In products like After Effects (I do post production work among other things) aligning one over the other is pretty straight forward but I am having a seniors moment with this.

I suspect the answer is somewhere in moving the centre x, y / anchor x, y point but am not certain.  Unfortunately, the internet assumes that noobs like me would know how to crop an image so that the different images align and so I couldn't find much on this particular problem.

Of course, it's always a bit embarrassing posting a question to a group of highly skilled folks so please forgive in advance.

Pete

9
Great Macro / Spreadsheet and many thanks for taking the time to produce and share.

10
General / Re: Batch edit fits headers
« on: 2018 July 20 00:14:28 »
Apologies for raising an older thread, but thought it might be useful to provide some feedback.

I recently had cause to change the focal length in the FITS header for a series of shots taken back in 2017.  I was just starting to use SGP and really had not much of an idea of what I was doing (a bit like I am with PI right now).  Anyway, for some reason my focal length was set to 517mm in stead of 714mm per the ES ED102CF I have.

Anyway, after some reading and assistance from Rob for pointing me in the right direction, I eventually found and ran the script to change the focal length accordingly.  I found some interesting results however. 

Running the script on either my High Sierra iMac, or Win 10Pro PC, the script would append a . on the end of the digit so instead of getting 714 the value was 714.  Given it is a digit, it may well treat 714. as 714.00 therefore making no difference at all, but still thought it might be worth pointing out.

Pete

11
Bug Reports / Re: FITSKeywords.js - assignment error
« on: 2018 July 18 17:21:33 »
Thanks mate, appreciate it after following the repository update instructions, and no updates provided, I wrongly assurmed that was it.

Thanks again Rob,

Pete

12
Announcements / Re: Price
« on: 2018 July 18 00:26:50 »
While I completely understand budget constraints (applies to me too), I would be totally lost in getting the best out of my images with without PI.

I’ll be honest, the learning curve does my head in, but well worth the effort.

Mate, you won’t look back.

13
Bug Reports / Re: FITSKeywords.js - assignment error
« on: 2018 July 18 00:13:17 »
Hi Rob,

Nice to hear from you again.

This is the thread from where I think this script grew:

https://pixinsight.com/forum/index.php?topic=9721.0

I admit this the fitsheader script grew out of this is an assumption on my part.

Pete

14
Apologies for the late inclusion...

Dimitris,

Just wondering if you have had a chance to add some notes your great presentation.  There are so few 'pure' NB tutorials around (I think folks assume anyone with NB knows what they are about - that is so no me!).

Pete

15
Bug Reports / FITSKeywords.js - assignment error
« on: 2018 July 17 20:25:46 »
Hi Team,

Now, this may or may not be a bug as I am not the worlds greatest Javascript user.   However, for the purposes of reporting, I provide the following:
I am looking to change the focal length of a series of images taken when I first started using SGP.  Unfortunately, I did not know enough about the product at the time to realise I needed to set the correct focal length of my train so in stead of 714mm (ES ED102CF), I somehow got 571 for all my images.  It was quite a while ago so not sure what I did back then.

In any event, I read the forums regarding batch processing changes to FITSKeywords and it eventually led me to the FITSKeywords script (I started manually changing FOCALLEN but that is going to get painful with the amount of images I have).

Besides not knowing how to actually batch change using FITSKeywords, I can load images, set an output directory and check the box that brings up FOCALLEN but cannot for the lift of me figure how to change the parameter from 571 to the correct 714mm.  I noted in Process Console the following error and wondered if that might have something to do with it:

run --execute-mode=auto "/Applications/PixInsight/src/scripts/FITSKeywords.js"

Processing script file: /Applications/PixInsight/src/scripts/FITSKeywords.js
 
** Warning [156]: /Applications/PixInsight/src/scripts/FITSKeywords.js, line 574: assignment to undeclared variable I

For information (and any suggestions),

I should add, I am running Mac OS 10.13.6 (High Sierra) on a late 2012 iMac 27"

Pete

Pages: [1] 2