NickK

So, after much pfaffing - my C++/OpenCL pipeline implementation is just starting to come alive! :D Previously it was using Apple GCD, however it quickly became clear that GCD's ability to sort out it's concurrency (it has it's own cl_command_queue) isn't strong part.. but I'm happy that it's starting to execute kernels and it shouldn't be too long before the pipeline is back at full tilt with some much needed OO refactoring :) This makes it rather portable too :D

Source: Garden Pier.. http://stargazerslounge.com/topic/226305-garden-pier/page-3 Happy that I, finally, have this done. I've also put on a rapid curing cement in the hole. Currently sat waiting - just to see if we're ok for polar alignment :D

Thank you :) Tomorrow is the last day of work and I already have tuesday mapped out to get things going on the job hunt.. will start applying immediately but for the first week I will take it a little slower. I had some interest - although they themselves are effectively a small contracting consultancy.. Good guys but not quite the level of stability I'm looking for. On the driver front - from past experience it's a crappy long list of applications coming up.. but you sometimes get periods where there's a gap so I can focus on doing some work at that point.

There is nothing that is 100% secure. Secure environments factor in the following: * Layers - like an onion * Time to get past each layer equates to a longer time to detect * Effective detection at each layer * Action on detection * Defence against disablement So starting with your fence, then the space between the fence and the obsy, then the obsy, then the space within the obsy (i.e. locked away components), then the larger stuff itself. On the disablement - ensuring that wires are not accessible, that having multiple ways to detect and that disabling one doesn't cause a failure of the the other detectors - i.e. pressure pads and sensors that don't go to an easily disabled point.

I seem to be having some interest.. but not counting chickens..

Got a call, I was sort of expecting, that my role is being put at risk.. so the drivers are taking a back seat until I've managed to get some security back. Long road, travelled before, but still never nice to hear those words.

Hi James, OSX only but .. I've just upgraded to 10.9 and have been reading through the AppNap documentation - have you checked out NSProcessInfo API in 10.9? One of the methods relates to categorising processing being done by the application (ProcessInfo beginActivityWithOptions:reason: etc) but also there's a section in the documentation about I/O prioritisation for latency such as video I/O. Although I think the Prevent AppNap finder option also helps but I think this will eventually become 'less optional'.. Still digging..

So the GPU version _had_ a few annoying bugs that caused it to crash the GPU.. but after an hour or so of bug fixing.. it lives! http://stargazerslounge.com/topic/218697-atik-titan-gets-a-17fps-realtime-registration-test-d/ When I have time I'll get the camera out on a lens/scope and get a proper image but for tonight that's good enough :D

Hmm good point..

However… OSX 10.9 supports OpenCL on the Intel chips too.. so it'll work on the mac mini (although slower as it's using system ram).

More fun is the MBP 2011 GPU cooling is borderline.. because image processing is almost infinitely parallel.. the GPU gets toasty! This version of the MBP has an issue with insufficient cooling.. may have to have a "slow it down a bit" button to maintain a temperature that won't cause a GPU crash due to temperature.

I'd still use the drivers.. just in case there's some changes/specialisations in there.

Awesome.. ATIK GP should work too

You know you're pushing the boundaries when the development tools get scared.. GuardMalloc[ExampleApplication-42660]: If you really wanted to allocate so much memory, launch your executable with the environment variable MALLOC_PERMIT_INSANE_REQUESTS set to any value to circumvent this check. GuardMalloc[ExampleApplication-42660]: Explicitly trapping into debugger!!! GuardMalloc[ExampleApplication-42660]: Attempting excessively large memory allocation: 268435456 bytes GuardMalloc[ExampleApplication-42660]: If you really wanted to allocate so much memory, launch your executable with the environment variable MALLOC_PERMIT_INSANE_REQUESTS set to any value to circumvent this check. This isn't an error.. it doesn't stop anything working..

Just a couple of things - the current isn't going to cause a problem. I've had a 100Ah car battery that normally outputs 800A for land rover starts. Current flows so it's the voltage that you need to work on. It's a good camera, although USB 1.1 speeds. You'll need to find out what range of exposures will get you into the range. Putting a simple lens on it works well for that.

Is the firmware a Cypress based chip download?

That's a great question, where do I go from here? To Procence, actually. My rig will be transported down to the new remote observatory this summer where it will share roof with 3 remote rigs. My horrible Swedish seeing is holding me back too much since I want to fully unleash my rigs potential under perfect skies. Everyone who've visited Olly Penrice's location knows what I'm talking about, there's no coincidence so much astronomy goes on in that region. So with significantly darker skies and probably 4 times as many clear nights as my part of Sweden, I will probably start doing real big & crazy(stupid) projects since I have a hard time saying no to challanges. & I belive Mr.Penrice once dared me to make a full mosaic of the entire cygnus-loop at this resolution, so yeah, I'm just getting started So Olly will need a new dedicated internet connection for the mass of image data being moved!! The image really shows what is possible..

Workload at work is current about 250%.. covering for boss and getting product launched means working from home to save time travelling.. 7am, shower,breakfast, enter office… quick lunch at 12 and then often sandrine only sees going to bed.. very little time to read forums let alone do any programming atm.. Next week it should ease off.. a bit..

In time for some SGL star party usage! http://stargazerslounge.com/topic/192900-atik-osx-drivers-r100-example-app/?p=2263424 A lot of water has passed under the bridge since 1.00, this latest release shows a real jump between 1.00 and now - it feels like a stepping stone. Perhaps a little bit of a pause after the 10.6.8 release considering some of my driver code goes back to 2011! I have many ideas and rework under the hood within ExampleApp is almost providing a base for these. However I have to balance these with ever growing demand on my time from work and home.