Upgrade to AMD Ryzen Threadripper 1950X 16 Core Processor

Yes I upgraded my desktop that I primarily use for processing my astrophotos and did a little bit of PixInsight benchmark and here are the results.

UPDATE

While doing a lot of performance optimization to my rig, I noticed some slow performance and wasn’t really happy with it so I decided to do a clean install once again.  We’ll this time the rig is more stable and the recent results for the PixInsight benchmark proved my findings.  With a gain of 3,713 points of the total performance score with a little bit of a tweak and installing the system on the M2 drive proved it’s worth effort.

Benchmark Identification
Serial number 42Y6JYDBBN49COCVJTK35W8HB2F91HDR
Benchmark version 1.00.08
Report date 2017/12/30 08:30:44 UTC
CPU Identification
CPU vendor AuthenticAMD
CPU model AMD Ryzen Threadripper 1950X 16-Core Processor
System Information
Platform Windows
Operating system Microsoft Windows 10 Pro
Core version PixInsight Core 01.08.05.1353 (x64)
Logical processors 32
Total memory size 31.900 GiB
Execution Times
Total time 42.58 s
CPU time 27.42 s
Swap time 15.14 s
Swap transfer rate 1094.710 MiB/s
Performance Indexes
Total performance 11047
CPU performance 13805
Swap performance 6063
Additional Information
Swap disks Samsung EVO 960
Motherboard Gigabyte Aorus X399 Gaming 7
Machine description AMD Ryzen Threadripper 1950X 16 Cores
Corsair Dominator Extreme Memory
Comments
Benchmark Identification
Serial number 78I5Z4GL214EGGRWU5737JK6966BJ722
Benchmark version 1.00.08
Report date 2017/12/27 17:49:54 UTC
CPU Identification
CPU vendor AuthenticAMD
CPU model AMD Ryzen Threadripper 1950X 16-Core Processor
System Information
Platform Windows
Operating system Microsoft Windows 10 Pro
Core version PixInsight Core 01.08.05.1353 (x64)
Logical processors 32
Total memory size 31.900 GiB
Execution Times
Total time 64.14 s
CPU time 30.58 s
Swap time 33.53 s
Swap transfer rate 494.358 MiB/s
Performance Indexes
Total performance 7334
CPU performance 12376
Swap performance 2738
Additional Information
Swap disks Samsung EVO 950 M.2
Motherboard Gigabyte Aorus X399 Gaming 7
Machine description AMD Ryzen ThreadRipper 1950X 16-Core CPU
NVidia GeForce GTX 1050 Ti
Comments Built my own processing machine for PixInsight

 

The California Nebula

The California Nebula

Taken under two hours of total integration time and yet was able to come up with a very good detail of the nebulosity.  Also this was a quick and dirty processing, nothing special in PinInsight and not even processed in Photoshop.  All was done with this image is just a simple PixelMath for combining the images from Ha and S2 filter data.  Will update this post as I’m still collecting data.

Testing the Tamron 18-400mm F/3.5-6.3 Di II VC HLD

I recently purchased the Tamron 18-400mm F/3.5-6.3 Di II VC HLD lens for my canon.  I tested it using the SL1 and 7D that has the cropped sensor.  I was amazed with the result and it’s truly at 22.2x zoom.

https://www.flickr.com/photos/bertandmai/37659856664/in/dateposted-public/

@18mm

35mm

@35mm

 

50mm

@50mm

 

70mm

@70mm

 

100mm

@100mm

 

200mm

@200mm

 

300mm

@300mm

 

400mm

@400mm

The images above are not processed, no correction, without any filter, etc.  This is just a demonstration of the zoom capability of the lens.  All shots are handheld with only the VC turned On.

The Wizard Nebula (NGC 7380)

This is becoming my another favorite.  I’ve struggled with capturing and processing this object, partly because of weather and because of equipment malfunction.  The first try was good enough but I realized the sulfur-2 data was bad and processing made it like a nightmare because of all the stars.

The Wizard Nebula is located some 7200 light years away and is surrounded by developing star clusters.  With this latest image, instead of removing the stars, I felt like the stars are actually making the image really look different, different from others.  I love the color of the stars and see the dust lanes glowing because of the starlight.

The Wizard Nebula

Equipment

  • ZWO ASI1600MM-Cool
  • ZWO 8 position 1.25″ EFW
  • Orion Narrowband filters (Ha, O3, S2) 7nm bandpass
  • Orion Atlas EQ-G Mount
  • Orion ED80T-CF
  • Orion SSAG (Guide Cam)
  • Orion 80mm Short Tube (Guide Scope)
  • EQ Focuser
  • EQ Switch

Capture and Processing

  • Sequence Generator Pro
  • PixInsight
  • Photoshop CC 2018

Sub/Frames Information

  • Ha – 44 x 300 secs
  • O3 – 42 x 300 secs
  • S2 – 60 x 300 secs
  • Dark – 40
  • bias – 50

EQFocuser – Instructions

EQFocuser Description

The EQFocuser started as a DIY project powered by Arduino and ASCOM.  It is completely compliant with ASCOM and so far this is the focuser that I’m using with my telescopes.  I have a couple of variations that are using different types of motor depending on the need.  The project is open source and you can download the drivers and sketch files here https://github.com/EverettQuebral/EQFocuser

Supported Stepper Motor Controller

Hardware Parts

  • 1 Arduino (Nano – $5.00, Uno – $8.00)
  • 1 Telescope specific bracket (I 3D printed mine)
  • Set of screws for your focuser
  • Aluminum Flexible Shaft Coupling ($1.50) (Please select the size for your focuser)
  • 2 Pull Up Switch (Optional)
  • 1 Variable Resistor (Optional)
  • 1 DHT11 (Temperature/Humidity) Sensor (Optional)

For EasyDriver or Adafruit Motor/Stepper/Servo Sheild

For ST35 or 28BYJ-48

 

Diagrams

Diagram Using ULN2003 Motor Driver

ULN 2003 Motor Driver

Diagram Using EasyDriver

EasyDriver Pins

The video above shows the NEMA 17 0.4AMP with 56.7oz.in torque

Github Location

https://github.com/EverettQuebral/EQFocuser

Driver Download

You can download the latest Driver at the Release section https://github.com/EverettQuebral/EQFocuser/releases

3D Model Files

Available under the Resources folder

Sequence Generator Pro PlateSolve Problem

I’ve been struggling with this situation in SGP and lost a lot of nights because of this issue.  See the movie with the SGP log below

[10/27/17 22:05:10.201][DEBUG] [Camera Thread] =========== Save file took 356 ms
[10/27/17 22:05:10.201][DEBUG] [Camera Thread] SGM_CAMERA_PLATE_SOLVER_CAPTURE complete…
[10/27/17 22:05:10.423][DEBUG] [Telescope Thread] Auto center verification frame complete. Plate solving image C:\Users\raina\AppData\Local\SequenceGenerator\Temp\plate_solve_image-1.fit
[10/27/17 22:05:10.504][DEBUG] [Telescope Thread] ************* SOLVE HINTS ****************
[10/27/17 22:05:10.504][DEBUG] [Telescope Thread] SOLVER: PlateSolve2
[10/27/17 22:05:10.504][DEBUG] [Telescope Thread] BLIND: False
[10/27/17 22:05:10.504][DEBUG] [Telescope Thread] METHOD: Max Regions
[10/27/17 22:05:10.504][DEBUG] [Telescope Thread] RA: 22.786322593689
[10/27/17 22:05:10.504][DEBUG] [Telescope Thread] DEC: 58.1384253501892
[10/27/17 22:05:10.504][DEBUG] [Telescope Thread] SCALE: 1
[10/27/17 22:05:10.504][DEBUG] [Telescope Thread] ******************************************
[10/27/17 22:05:10.510][DEBUG] [Telescope Thread] FitsFileHeaderData: Angle – 0
[10/27/17 22:05:10.510][DEBUG] [Telescope Thread] FitsFileHeaderData: Scale – 0
[10/27/17 22:05:10.510][DEBUG] [Telescope Thread] FitsFileHeaderData: RA – 22.7862467765808
[10/27/17 22:05:10.510][DEBUG] [Telescope Thread] FitsFileHeaderData: DEC – 58.1384682655334
[10/27/17 22:05:10.510][DEBUG] [Telescope Thread] PlateSove2 Param: RA (RAD) – 5.9654453052217
[10/27/17 22:05:10.510][DEBUG] [Telescope Thread] PlateSove2 Param: DEC (RAD) – 1.01470694428574
[10/27/17 22:05:10.510][DEBUG] [Telescope Thread] PlateSove2 Param: Width – 2328
[10/27/17 22:05:10.510][DEBUG] [Telescope Thread] PlateSove2 Param: Height – 1760
[10/27/17 22:05:10.510][DEBUG] [Telescope Thread] PlateSolve2 Command Line:
[10/27/17 22:05:10.510][DEBUG] [Telescope Thread] C:\Users\raina\AppData\Local\SequenceGenerator\\PlateSolve2.exe 5.96544530522170,1.01470694428574,0.01128646249623,0.00853272078753,3000,C:\Users\raina\AppData\Local\SequenceGenerator\\Temp\psXSolve_1.fit
[10/27/17 22:05:16.188][DEBUG] [Telescope Thread] *********** SUCCESSFUL SOLVE *************
[10/27/17 22:05:16.188][DEBUG] [Telescope Thread] SOLVER: False
[10/27/17 22:05:16.188][DEBUG] [Telescope Thread] SUCCESS: True
[10/27/17 22:05:16.188][DEBUG] [Telescope Thread] CONF: 307
[10/27/17 22:05:16.188][DEBUG] [Telescope Thread] BLIND: False
[10/27/17 22:05:16.188][DEBUG] [Telescope Thread] RA: 22.7867192515237
[10/27/17 22:05:16.188][DEBUG] [Telescope Thread] DEC: 58.1428305771212
[10/27/17 22:05:16.188][DEBUG] [Telescope Thread] SCALE: 3.23906
[10/27/17 22:05:16.188][DEBUG] [Telescope Thread] FLIPPED: False
[10/27/17 22:05:16.188][DEBUG] [Telescope Thread] ANGLE (EON): 89.96
[10/27/17 22:05:16.188][DEBUG] [Telescope Thread] MSG: Valid solve.
[10/27/17 22:05:16.188][DEBUG] [Telescope Thread] ******************************************
[10/27/17 22:05:16.189][DEBUG] [Telescope Thread] Checking to see if solve might be bad…
[10/27/17 22:05:16.189][DEBUG] [Telescope Thread] Solved scale not within 25% of scale hint!
[10/27/17 22:05:16.189][DEBUG] [Telescope Thread] Solve might be bad (auto center)! Solved scale is not within 25% of scale hint.
[10/27/17 22:05:26.157][DEBUG] [Telescope Thread] Sequence aborted due to possible bad solve…
[10/27/17 22:05:26.157][DEBUG] [Telescope Thread] Adding sequence level notification: A Plate solve during auto center might be bad! Sequence aborted (or entered recovery mode)!