Free 2x software for mac

The CUDA Toolkit is a C language development environment for CUDA-enabled GPUs.
In a matter of a few years, the programmable graphics processor unit has
developed into an absolute computing workhorse. With multiple cores driven by very high memory bandwidth, todays GPUs offer incredible resources for both graphics and non-graphics processing.
The main reason behind such an evolution is that the GPU is specialized for compute-intensive, highly parallel computation exactly what graphics rendering is about and therefore is designed such that more transistors are devoted to data processing rather than data caching and flow control.
The CUDA development environment includes:
- nvcc C compiler
- CUDA FFT and BLAS libraries for the GPU
- Profiler
- gdb debugger for the GPU (alpha available in March, 2008)
- CUDA runtime driver (now also available in the standard NVIDIA GPU driver)
- CUDA programming manual
The CUDA Developer SDK provides examples with source code to help you get started with CUDA. Examples include:
- Parallel bitonic sort
- Matrix multiplication
- Matrix transpose
- Performance profiling using timers
- Parallel prefix sum (scan) of large arrays
- Image convolution
- 1D DWT using Haar wavelet
- OpenGL and Direct3D graphics interoperation examples
- CUDA BLAS and FFT library usage examples
- CPU-GPU C- and C++-code integration
- Binomial Option Pricing
- Black-Scholes Option Pricing
- Monte-Carlo Option Pricing
- Parallel Mersenne Twister (random number generation)
- Parallel Histogram
- Image Denoising
- Sobel Edge Detection Filter
- MathWorks MATLAB Plug-in

Main features:
- Standard C programming language enabled on a GPU.
- Unified hardware and software solution for parallel computing on CUDA-enabled NVIDIA GPUs.
- CUDA compatible GPUs range from lower power notebook GPUs to high performance, multi-GPU systems.
- CUDA-enabled GPUs support the Parallel Data Cache and Thread Execution Manager.
- Standard numerical libraries for FFT (Fast Fourier Transform) and BLAS (Basic Linear Algebra Subroutines).
- Dedicated CUDA driver for computing.
- Optimized direct upload and download path from the CPU to CUDA-enabled GPU.
- CUDA driver interoperates with OpenGL and DirectX graphics drivers.
- Support for Linux 32/64-bit and Windows XP 32/64-bit operating systems.
- Direct driver and assembly level access through CUDA for research and language development.

Enhancements
- Visual Profiler for the GPU - The most common step in tuning application performance is profiling the application and then modifying the code. The CUDA Visual Profiler is a graphical tool that enables the profiling of C applications running on the GPU. This latest release of the CUDA Visual Profiler includes metrics for memory transactions, giving developers visibility into one of the most important areas they can tune to get better performance.
- Improved OpenGL Interop - Delivers improved performance for Medical Imaging and other OpenGL applications running on Quadro GPUs when computing with CUDA and rendering OpenGL graphics functions are performed on different GPUs.
- Texture from Pitch Linear Memory - Delivers up to 2x bandwidth savings for video processing applications.
- Zero-copy - Enables streaming media, video transcoding, image processing and signal processing applications to realize significant performance improvements by allowing CUDA functions to read and write directly from pinned system memory. This reduces the frequency and amount of data copied back and forth between GPU and CPU memory. Supported on MCP7x and GT200 and later GPUs.
- Pinned Shared Sysmem - Enables applications that use multiple GPUs to achieve better performance and use less total system memory by allowing multiple GPUs to access the same data in system memory. Typical multi-GPU systems include Tesla servers, Tesla Personal Supercomputers, workstations using QuadroPlex deskside units and consumer systems with multiple GPUs.
- Asynchronous memcopy on Vista - Allows applications to realize significant performance improvements by copying memory asynchronously. This feature was already available on other supported platforms but is now available on Vista.
- Hardware Debugger for the GPU - Developers can now use a hardware level debugger on CUDA-enabled GPUs that offers the simplicity of the popular open-source GDB debugger yet enables a developer to easily debug a program that is running 1000s of threads on the GPU. This CUDA GDB debugger for Linux has all the features required to debug directly on the GPU, including the ability to set breakpoints, watch variables, inspect state, etc.
- Exclusive Device Mode - This system configuration option allows an application to get exclusive use of a GPU, guaranteeing that 100% of the processing power and memory of the GPU will be dedicated to that application. Multiple applications can still be run concurrently on the system, but only one application can make use of each GPU at a time. This configuration is particularly useful on Tesla cluster systems where large applications may require dedicated use of one or more GPUs on each node of a Linux cluster.
Pinned Memory Support:
- These new memory management functions (cuMemHostAlloc() and cudaHostAlloc()) enable pinned memory to be made "portable" (available to all CUDA contexts), "mapped" (mapped into the CUDA address space), and/or "write combined" (not cached and faster for the GPU to access).
- cuMemHostAlloc
- cuMemHostGetDevicePointer
- cudaHostAlloc
- cudaHostGetDevicePointer
Function attribute query:
- This function allows applications to query various function properties.
- cuFuncGetAttribute
2D Texture reads from pitch linear memory:
- You can bind linear memory that you get from cuMemAlloc() or cudaMalloc() directly to a 2D texture. In previous releases, you were only able to bind cuArrayCreate() or cudaMallocArray() arrays to 2D textures.
- cuTexRefSetAddress2D
- cudaBindTexture2D
Flags for event creation:
- Applications can now create events that use blocking synchronization.
- cudaEventCreateWithFlags
New device management and context creation flags:
- The function cudaSetDeviceFlags() allows the application to specify attributes such as mapping host memory and support for blocking synchronization.
- cudaSetDeviceFlags
Improved runtime device management:
- The runtime now defaults to attempting context creation on other devices in the system before returning any failure messages. The new call cudaSetValidDevices() allows the application to specify a list of acceptable devices for use.
- cudaSetValidDevices
Driver/runtime version query functions:
- Applications can now directly query version information about the underlying driver/runtime.
- cuDriverGetVersion
- cudaDriverGetVersion
- cudaRuntimeGetVersion
New device attribute queries:
- CU_DEVICE_ATTRIBUTE_INTEGRATED
- CU_DEVICE_ATTRIBUTE_CAN_MAP_HOST_MEMORY
- CU_DEVICE_ATTRIBUTE_COMPUTE_MODE
Documentation:
- Doxygen-generated and cross-referenced html, pdf, and man pages.
- Runtime API
- Driver API

OsiriX 3.6.1 offers an innovative, versatile image processing software dedicated to DICOM images produced by medical equipment (MRI, CT, PET, PET-CT, ...) and confocal microscopy (LSM and BioRAD-PIC format). It can also read many other file formats: TIFF (8,16, 32 bits), JPEG, PDF, AVI, MPEG and Quicktime. It is fully compliant with the DICOM standard for image comunication and image file formats. OsiriX is able to receive images transferred by DICOM communication protocol from any PACS or medical imaging modality (STORE SCP - Service Class Provider, STORE SCU - Service Class User, and Query/Retrieve) .

OsiriX has been specifically designed for navigation and visualization of multimodality and multidimensional images: 2D Viewer, 3D Viewer, 4D Viewer (3D series with temporal dimension, for example: Cardiac-CT) and 5D Viewer (3D series with temporal and functional dimensions, for example: Cardiac-PET-CT). The 3D Viewer offers all modern rendering modes: Multiplanar reconstruction (MPR), Surface Rendering, Volume Rendering and Maximum Intensity Projection (MIP). All these modes support 4D data and are able to produce image fusion between two different series (for example: PET-CT).

Osirix is at the same time a DICOM PACS workstation for medical imaging and an image processing software for medical research (radiology and nuclear imaging), functional imaging, 3D imaging, confocal microscopy and molecular imaging.

Osirix supports a complete plug-ins architecture that allows you to expand the capabilities of OsiriX for your personal needs! This plug-in architecture gives you access to the powerfull Cocoa framework with an easy object-oriented and dynamic language: Objective-C.

Blackmarket's JukeboxMM 1.3b provides users with a useful and easy-to-use full screen front-end Jukebox for SoundJam MP. Uses 2x copies of SoundJam MP to act as 2x decks. Imports a SoundJam MP exported playlist. Supports playlists, top ten, mixing, random play.

Requirements:

• PPCMac OS 8.6 or higher
• SoundJamQuickTime

Bazaar is a distributed version control system available under the GPL that reduces barriers to participation in your project.
Bazaar is designed to support Mac OS, GNU/Linux, UNIX, Windows. In summary, Bazaar gives you fast, distributed revision control that "Just Works", supporting renames of directories and files smoothly.
Bazaar is designed to maximise the level of community participation in your project.
Bazaar branches can be published on any web server, and uploaded over sftp, ftp, or rsync. If you want the fastest possible network performance, there is a smart server.
Bazaar supports flexible work models: centralized like cvs or svn, commit offline, enforced code review when desired, and automatic regression testing.
Decentralized revision control systems give people the ability to collaborate more efficiently over the internet using the bazaar development model and have many other advantages.
When you use Bazaar, you can commit to your own local branches of your favourite free software projects without needing special permission.

Main features:
Good performance:
- Bazaar status in a tree of 5,000 files takes just 0.5 seconds, so almost every open source project can get the advanced features of Bazaar without slowing down its developers. Bazaar is robust in the face of radical tree restructuring, saving you time when it comes to merging from your community.
Safe with your data:
- There have not been any data loss bugs in a Bazaar release in the past two years. Bazaar has a huge test suite that ensures that new file formats can be tested automatically. The development process follows best practice with code review of all core and community code landings.
Friendly:
- Bazaar "Just Works" (which is why the Ubuntu team chose it for their project). Bazaar has a natural feel, you can publish your code on any web server or use a custom server for performance. Bazaar has perfect support for renaming files AND directories, which means you can unleash your community and merge efficiently even from contributors who are radically restructuring the tree.
Free:
- Bazaar is available under the GPL v2 or later.
Easy to integrate:
- Bazaar is designed as a Python API with a plugin system, so it is easy to embed in your tools and projects and easy to extend or integrate with existing infrastructure. Whether you are managing your development, or keeping track of configuration files, or building a new content management system, Bazaar is a great choice if you like to work in Python.

System requirements:
-

Enhancements
Compatibility Breaks:
- Display prompt on stderr (instead of stdout) when querying users so that the output of commands can be safely redirected. (Vincent Ladeuil, #376582)
New Features:
- A new repository format 2a has been added. This is a beta release of the the brisbane-core (aka group-compress) project. This format now suitable for wider testing by advanced users willing to deal with some bugs. We would appreciate test reports, either positive or negative. Format 2a is substantially smaller and faster for many operations on many trees. This format or an updated version will become the default in bzr 2.0.
- This is a rich-root format, so this repository format can be used with bzr-svn. Bazaar branches in previous non-rich-root formats can be converted (including by merge, push and pull) to format 2a, but not vice versa. We recommend upgrading previous development formats to 2a.
- Upgrading to this format can take considerable time because it expands and more concisely repacks the full history.
- If you use stacked branches, you must upgrade the stacked branches before the stacked-on branches. (See )
- --development7-rich-root is a new dev format, similar to --dev6 but using a Revision serializer using bencode rather than XML. (Jelmer Vernooij, John Arbash Meinel)
- mail_client=claws now supports --body (and message body hooks). Also uses configured from address. (Barry Warsaw)
Improvements:
- --development6-rich-root can now stack. (Modulo some smart-server bugs with stacking and non default formats.) (John Arbash Meinel, #373455)
- --development6-rich-root delays generating a delta index for the first object inserted into a group. This has a beneficial impact on bzr commit since each committed texts goes to its own group. For committing a 90MB file, it drops peak memory by about 200MB, and speeds up commit from 7s => 4s. (John Arbash Meinel)
- Numerous operations are now faster for huge projects, i.e. those with a large number of files and/or a large number of revisions, particularly when the latest development format is used. These operations (and improvements on OpenOffice.org) include: branch in a shared repository (2X faster), branch --no-tree (100X faster), diff (2X faster), tags (70X faster) (Ian Clatworthy)
- Pyrex version of bencode support. This provides optimized support for both encoding and decoding, and is now found at bzrlib.bencode. bzrlib.utils.bencode is now deprecated. (Alexander Belchenko, Jelmer Vernooij, John Arbash Meinel)
Bug Fixes:
- Bazaar can now pass attachment files to the mutt email client. (Edwin Grubbs, #384158)
- Better message in bzr add output suggesting using bzr ignored to see which files can also be added. (Jason Spashett, #76616)
- bzr pull -r 123 from a stacked branch on a smart server no longer fails. Also, the Branch.revision_history() API now works in the same situation. (Andrew Bennetts, #380314)
- bzr serve on Windows no longer displays a traceback simply because a TCP client disconnected. (Andrew Bennetts)
- Clarify the rules for locking and fallback repositories. Fix bugs in how RemoteRepository was handling fallbacks along with the _real_repository. (Andrew Bennetts, John Arbash Meinel, #375496)
- Fix a small bug with fetching revisions w/ ghosts into a new stacked branch. Not often triggered, because it required ghosts to be part of the fetched revisions, not in the stacked-on ancestry. (John Arbash Meinel)
- Fix status and commit to work with content filtered trees, addressing numerous bad bugs with line-ending support. (Ian Clatworthy, #362030)
- Fix problem of "directory not empty" when contending for a lock over sftp. (Martin Pool, #340352)
- Fix rule handling so that eol is optional, not mandatory. (Ian Clatworthy, #379370)
- Pushing a new stacked branch to a 1.15 smart server was broken due to a bug in the BzrDirFormat.initialize_ex smart verb. This is fixed in 1.16, but required changes to the network protocol, so the BzrDirFormat.initialize_ex verb has been removed and replaced with a corrected BzrDirFormat.initialize_ex_1.16 verb. 1.15 clients will still work with a 1.16 server as they will fallback to slower (and bug-free) methods. (Jonathan Lange, Robert Collins, Andrew Bennetts, #385132)
- Reconcile can now deal with text revisions that originated in revisions that are ghosts. (Jelmer Vernooij, #336749)
- Support cloning of branches with ghosts in the left hand side history. (Jelmer Vernooij, #248540)
- The bzr diff now catches OSError from osutils.rmtree and logs a helpful message to the trace file, unless the temp directory really was removed (which would be very strange). Since the diff operation has succeeded from the users perspective, no output is written to stderr or stdout. (Maritza Mendez, #363837)
- Translate errors received from a smart server in response to a BzrDirFormat.initialize or BzrDirFormat.initialize_ex request. This was causing tracebacks even for mundane errors like PermissionDenied. (Andrew Bennetts, #381329)
Documentation:
- Added directory structure and started translation of docs in Russian. (Alexey Shtokalo, Alexander Iljin, Alexander Belchenko, Dmitry Vasiliev, Volodymyr Kotulskyi)
API Changes:
- Added osutils.parent_directories(). (Ian Clatworthy)
- bzrlib.progress.ProgressBar, ChildProgress, DotsProgressBar, TTYProgressBar and child_progress are now deprecated; use ui_factory.nested_progress_bar instead. (Martin Pool)
- graph.StackedParentsProvider is now a public API, replacing graph._StackedParentsProvider. The api is now considered stable and ready for external users. (Gary van der Merwe)
- bzrlib.user_encoding is deprecated in favor of get_user_encoding. (Alexander Belchenko)
- TreeTransformBase no longer assumes that limbo is provided via disk. DiskTreeTransform now provides disk functionality. (Aaron Bentley)
Internals:
- Remove weave.py script for accessing internals of old weave-format repositories. (Martin Pool)
Testing:
- The number of cores is now correctly detected on OSX. (John Szakmeister)
- The number of cores is also detected on Solaris and win32. (Vincent Ladeuil)
- The number of cores is also detected on FreeBSD. (Matthew Fuller)