Scanning is an open source project for moving scientific instruments and writing NeXus (http://www.nexusformat.org/) compliant files. It is designed to be control system neutral, EPICS, TANGO etc. may be used. See https://projects.eclipse.org/proposals/scanning and https://github.com/eclipse/scanning/blob/master/GETTINGSTARTED.pdf
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
org.eclipse.scanning.api
org.eclipse.scanning.command
org.eclipse.scanning.connector.activemq.test
org.eclipse.scanning.connector.activemq
org.eclipse.scanning.connector.epics
org.eclipse.scanning.device.ui
org.eclipse.scanning.device
org.eclipse.scanning.event.queues.feature
org.eclipse.scanning.event.queues.spooler
org.eclipse.scanning.event.queues
org.eclipse.scanning.event.ui
org.eclipse.scanning.event
org.eclipse.scanning.example.feature
org.eclipse.scanning.example.messaging
org.eclipse.scanning.example.ui.feature
org.eclipse.scanning.example.xcen.test
org.eclipse.scanning.example.xcen.ui
org.eclipse.scanning.example.xcen
org.eclipse.scanning.example
org.eclipse.scanning.feature
org.eclipse.scanning.malcolm.core
org.eclipse.scanning.malcolm.feature
org.eclipse.scanning.points
org.eclipse.scanning.releng
org.eclipse.scanning.repository
org.eclipse.scanning.sequencer
org.eclipse.scanning.server
org.eclipse.scanning.target.platform
org.eclipse.scanning.test
org.eclipse.scanning.third.feature
org.eclipse.scanning.ui.feature
.gitattributes
.travis.yml
CONTRIBUTING.md
GETTINGSTARTED.pdf
LICENSE
README.md
SCANANATOMY.pdf
WHATISSCANNING.pdf
pom.xml

README.md

Eclipse Scanning

Build Status

Scanning is an open source project for moving scientific instruments and writing NeXus compliant files. It is designed to be control system neutral, EPICS, TANGO etc. may be used. See proposal and Getting Started

Adding Tests

The test system is linked into Travis CI and your pull request will be checked with the build and test. Tests should not be added in the same bundle that created the feature but in a .test bundle which may be a fragment of the original bundle. This enables the build to remove test code from the binary easily because those bundles are not in the feature. NOTE This has the added benefit that your test bunles or fragment may have dependencies which the main bundle does not. For instance in org.eclipse.scanning.test we depend on almost eveything imaginable but of course this bundle is not part of the binary product.

Instead of having to name your class *Test as in other projects, in this project you should add a Suite to each package of tests. This defines the tests that are run automatically in the build. This procedure allows for long running or CPU/threading tests to be ommited from a build to keep the run time down while waiting for the merge.

Example: org.eclipse.scanning.test.points.Suite

Check out a development version

  1. Clone repositories as specified in .travis.yml at the top of this repository (richbeans, dawnsci, dawn-hdf)
  2. Clone this repositiory to org.eclipse.scanning
  3. Import all the bundles from all the repos to your eclipse workspace (other IDE's are available but they probably don't support target platforms)
  4. Use the org.eclipse.scanning.target.platform target plaform which will pull in a few apacahe dependencies
  5. After setting this target as the target platform, your code should compile
  6. Start an apachemq on localhost:61616
  7. Run the example server and example client and go to the 'X-Ray Centering' example erspective or the 'Scanning' perspective.