Download Photo Solve
Inca Lillard
And there is even some directions to go with the plate solver. You must give an approximate RA and DEC (it can't do it blind) and when it is done, it writes the info to the image file. Then use the annotater to label the image. Pretty amazing. See the attached examples. In the following post, I show an example of the labeled image.
First, I was having trouble getting the plate solve script to work on some of my images. I would put in the focal length of my scope and the pixel size of the camera, but it would "blow up" and not solve the image. Then it occurred to me that the images I was using had been reduced in size. When I put in a corrected image scale (i.e., corrected for the fact that I had reduced the image size by 2/3, from 5094 x 3414 pixels to 1728 x 1158 pixels) it worked on every image. So my "native" image scale, which is about 1.38 arcsec/pixel, had to be entered as 4 arcsec/pixel for the resized (not cropped) image.
1. Under image analysis, use imagesolver. Three things to note. First, PI needs to know what portion of the sky you want labeled. Select search and put int he NDC, IC or star name for the field in question. It will usually be able to find it, but not always. Or you can just put in the RA and DEC. Second, the program needs to know the image scale you are using. This can be calculated if the program has the focal length in mm and the pixel size for your camera. Third, if you have a problem getting it to work, try a different star catalog. I usually set the limiting magnitude to 18. Once you have a solution, then go to step 2.
Hello Team,
I own a NEXSTAR EVOLUTION 8 HD TELESCOPE WITH STARSENSE. As you might have come across this Error from lot of folks, I wanted to raise this issue pertaining to Starsense Error Message I get "Could not plate-solve the image. Will retry at new position" even after "Found 100 stars" in Dark Sky Sites - absolute clear skies where I can see 100s of stars with my necked eyes.
Could I please request you to let me know how to resolve this issue. I was under the impression that after updating the Starsense Hand control and camera with the above (latest) version, it would resolve this issue. However, it still didn't get resolved. Also, I am planning to buy SkyPortal Pro or Plus, hence could you also please let me know if the issue will get resolved post updating it to SkyPortal Pro or Plus??
One last option for later on (after StarSense issue is solved) is to use something like CPWI or Starry Nights on a laptop connecting with a USB cable. If have a long session and great weather for several days, I really enjoy the more accurate pointing model in CPWI. I cover the rig in a Telegizmos 365 each night and "park" the scope in CPWI (Hibernate on HC), and as long as I haven't moved the mount or OTA, the alignment is already done!
mlord is a master but I'll add one: date, time, location, POWER. You might try getting back to basics until you solve the issue - just use the mount and HC. Add layers of tech (apps) after you master the process with just the basics.
But then my boss asked that we have a photo for each Volunteer attached to their information in AirTable. OK. I can do that with an attachment field. But then I decided that I wanted the Volunteers to do that data entry as well. So I created another form that works satisfactorily and allows them to use the same iPad to take a photo. They have the ability to choose their name because it is linked to the main table, and then do an on the spot upload of a photo taken by the iPad.
I just tried your solution. It seems like the setting affects the behavior in the Appsheet container app but not the browser version. As soon as I open my app on my smartphone in the browser, I can still choose a file instead of being forced to take a new photo even though I disabled "Allow image input from gallery".
This document contains basic troubleshooting steps that should solve most problems you can encounter while using Photoshop. Try all the steps below before posting on the forum for Photoshop-specific issues.
I've tried making the transparent layer wider, and did some changes in lighting, unchecked passepartout in camera(although that stated outside the image area). but that did not resolve it. Turning the sun off did make a change.
Luckily for me, I have never been a victim of a situation where I lost all of my data simply because I do backups regularly. I never do a full backup of my machine though. I can download an operating system in a few minutes, restore my system preferences with a single click, install all my frequently used apps using a single command, pull all of my projects from GitHub and listen to music on my Technics SL-1200 or stream it from Apple Music. The only thing that I keep backed up is my photo collection.
Are prices prorated, or do you get charged for a full month? For example, 1TB would cost $23/month in Standard, and $4/month in Glacial. Do you end up paying $23 for the 1 day your photos sit in Standard storage?
This is interesting and definitely worth looking at for some more automation freaks than me. I am kinda happy with my very manual process. I do it very rarely so automating this would be an overkill in my case. For professional photographers it is a really fantastic tool!
I'm not sure the server-side encryption is on by default though, and I think I had to specifically enable it in bucket settings, but it's there and it's as simple as turning it on. This way your girlfriend's photos are safe from anyone's, even the employee's eyes! :)
Thanks for the helpful article. I was looking into AWS for work and likewise thought maybe should expand my backups to use AWS rather than just a NAS and on site backup. However one point to consider is the fact that I got numerous warnings about how Glacier and Glacier Deep Archive are charged. Not only per request, but also per file, additional storage is required and it is very very hard to work out just what this means as far as $$ is concerned. Also I read each type has a minimum time of storage and you will be charged if you delete earlier than that time, which for GDA is 6 months. I have over 100,000 photos I was going to simply replicate to S3 and then push to GDA. I am now thinking that is a very bad idea and that I should perhaps zip them up or something but that creates additional problems around how many versions do you keep, how often you update, when do you delete, etc. I suggest that is why "simpler" options like Dropbox, Google, Drive, etc are popular as you just buy a bucket of storage and can upload, add, change, etc as much as you like without fear of racking up a large bill. If you know what you are doing and can understand the complicated charging model then perhaps S3 & AWS might work out cheaper.. but it could cost you a lot more as well!
I started using S3 a few years ago for both syncing across machines and operating systems and archival of documents, photos, music and video. I use it to host two static websites as well. There are easy to use GUIs (Transmit on Mac, Cloudberry Explorer on PC, Cyberduck, Filezilla, others both paid and "free") and the command line is easy to use with a wee bit of learning and patience. (It will be familiar to anyone who has worked with Linux.)
Your reminder to set up users beyond root is timely. I have neglected this but understand its importance. I have never explored Glacier but will look into it. Seems simple enough. One thing I've begun doing is backing up photos and other files directly from Android phone to S3 buckets. Haven't found a way to automate this though.
Thanks for the great and simple tutorial @pawelgrzybek:disqus! You really demystified AWS S3.
Can you go into greater detail on how to secure your S3 bucket? What are the IAM configurations you have in place for securing the photo backup?
Also, I read online that you can enter 0 for the days when creating the transition to Glacier rule, and that way it transfers the objects immediately. Do you have any experience with that?
* It can handle encryption, so everything you put into S3 is encrypted if you so choose, even to amazon itself.
* If can add another layer of metadata on top of your files managed in the tool itself. Then you can use that as search criteria in other commands, and even dynamically restructure the layout into temporary metadata driven views (think tagging people in photos, then dynamically restructuring the layout so all photos of people are in folders of their name, then switching it back as it was as if nothing happened).
* It can add multiple "backends" that include S3 but don't have to be. You can even store data in different cloud services and access them all from one place if you like. Moving them between services as you see fit (they all have free plans up to like 5gb right? :P ).
* Because it uses git as the backbone for syncing all the metadata and location info. You have all the knowledge completely offline. So you could check where a file lives, for instance, on a laptop offline on a beach somewhere, if you so desired. :P