[comp.windows.x] XVision Distribution

rasure@houdini.UUCP (John Rasure) (07/07/87)

The following describes how to obtain XVision.  The first part is
the standard licensing agreement that should be filled out and sent 
to the specified address.  The second part is a description of XVision.

XVision source will be sent to you on a 9-track tar tape along with
a set of manuals and other documentation.  We will begin sending 
copies on August 4th.

If you have questions, send them to:

	xvision@hc.dspo.gov
	{ucbvax,gatech,convex,pur-ee,lanl}unmvax!houdini!xvision


Note:  This is the first release of XVision, and we hope there will
be several more to come.  We decided to charge a distribution fee for
XVision so that we could maintain its quality and cover the costs
of providing it to the large number of people who have requested it.
We plan on using the Electronic mail addresses of the Licensees
to distribute additions and bug fixes.

************************************************************************


			SOFTWARE LICENSE AGREEMENT


  University of New Mexico, Department of Electrical and Computer Engineering


Agreement made this ________ day of ______________, 1987, between the
University of New Mexico acting though its Department of Electrical and
Computer Engineering (hereinafter referred to as the "EECE"), located in 
Albuquerque, New Mexico and

___________________________________________________________________________
an organization located in

___________________________________________________________________________
(hereinafter referred to as the "Licensee").


A.  LICENSE


1.  The EECE grants and the Licensee accepts, upon the terms and conditions
hereinafter set forth, a non-exclusive, non-transferable, and perpetual 
license to use the computer software system know as XVision Release 1.0 
(hereinafter referred to as the System), together with associated documentation.

2.  It is understood that the System is comprised of a number of software
components, some of which were authored and developed at institutions other
than the EECE.  Nothing in this Agreement is intended to supersede or reduce
the rights or obligations of the various institutions (hereinafter referred
to as the Sources) originating the components of the System.

B.  LICENSE FEE

1.  Upon execution of the Agreement, Licensee agrees to pay the EECE a 
distribution fee of $250.00, and a one-time license fee of $0.0.
All payments will be made by check or money order payable to Dept. of EECE, UNM;
and sent to XVision (Attn. Gladys Erickson), Department of Electrical and 
Computer Engineering, University of New Mexico, Albuquerque N.M. 87131.

2.  Upon acceptance of this Agreement by the EECE, the EECE agrees to deliver
to Licensee on machine-readable copy of the System, together with associated
documentation.

C.  USE RESTRICTIONS

1.  The Licensee agrees that neither the System or any of its components shall
be used as the basis of a commercial design tool product, and that it shall not 
be rewritten in another computer language or otherwise adapted to circumvent
the need for obtaining additional license rights.

2.  The license granted hereunder and the licensed System may not be assigned,
sublicensed, or otherwise transferred by the Licensee.  The Licensee shall
take reasonable precautions to ensure that neither the System or its
components are copied, transferred, or disclosed to parties other than the
Licensee.

3.  In no event shall the Licensee install or provide this System on any
computer system on which the Licensee purchases or sells computer-related
services.

4.  Nothing in this Agreement shall be construed as conferring rights to use
in advertising, publicity, or otherwise any trademark or the names of either
the EECE, the University of New Mexico, or any of the Sources.  Such use
requires prior approval in writing.

5.  Licensee is authorized to make one (1) copy of the system for back
up purposes.



D.  LIMITATION OF LIABILITY

1.  Neither the EECE nor the Sources make any warranties, either express or
implied, as to the condition of the System, its merchantability, or its
fitness for any particular purpose.  The Licensee agrees to accept the System
"as is" and it is understood that the EECE and Sources are not obligated to
provide maintenance, improvements, or support of any kind.

2.  The EECE and the Sources shall not be liable for any direct or 
consequential damages suffered by the Licensee or any other parties from the
use of the System.

3.  The Licensee agrees to indemnify the EECE for liability resulting from
the use of the System by Licensee.  The Licensee and the EECE each agree
to hold the other harmless for their own negligence.


E.  TITLE

1.  All intellectual property rights including, patent, copyright and 
trademark rights to the System are retained by the EECE and the Sources 
which authored the System.  The Licensee shall take all reasonable 
precautions to preserve these rights and do no acts in degradation of
these rights.

2.  The EECE and the Sources reserve the right to license or grant any other
rights to the System to other persons or entities.

3.  The System is the property of EECE and the Licensee has no rights
therein except as expressly printed herein.
				


F.  TERMINATION

1.  Subject to the provisions in 2. below, the Licensee and the EECE 
may mutually agree to terminate this Agreement at any time for any reason.

2.  In the event the EECE believes the Licensee has violated thee terms of
this Agreement, the EECE will inform the Licensee in writting of the possible
violation and the Licensee will have thirty (30) days from the date of such
notification to provide explanation or remedy satisfactory to the EECE.  The
Licensee agrees that if satisfactory explanation or remedy is not provided, 
the EECE may immediately terminate this Agreement.

3.  Licensee agrees that upon termination of this agreement it will return
the System to the Licenser or otherwise dispose of the System and its
copies as the Licenser instructs.


IN WITNESS WHEREOF, the parties hereto have executed this instrument as of the
dates given below:

University of New Mexico, Department of Electrical and Computer Engineering

	By    _____________________________________________

	Title _____________________________________________

	Date  _____________________________________________


	Licensee:

	By    _____________________________________________

	Title _____________________________________________

	Date  _____________________________________________

	Electronic Mail Address of Person who will 
	maintain the System: ______________________________

	___________________________________________________

	___________________________________________________


************************************************************************


The following contains a one page description of XVision. 

Outline
-------

1.  Overview
2.  Features
3.  System Requirements
4.  Future Plans


1.  OVERVIEW
------------

     XVision is a research and development tool designed to:
* facilitate investigation into new computer vision/image processing
  techniques and
* facilitate the development of turn key vision solutions for various
  application areas (automation, medicine, biology, astronomy, etc).

     XVision utilizes the X Window System, which provides a network
transparent windowing environment, and will soon be interfaced to
frame rate image processing hardware to provide the vision
programmer with a high-level, interactive vision system. 


2.  FEATURES
------------

2.1  Menuing system.  The menu system is based on Xmenu.  The menus
were designed to minimize the amount of user interaction; the
menus are reconfigured to reflect past actions and input from the
user.  The menu system controls all of the XVision capabilities and is
consistent from routine to routine.  As part of the menu system,
a command history is kept of the current session.  This history
can be used to build script files that can be used when an
interactive environment is not appropriate.

2.2  Image Processing Routines.  The routines are all separate C programs,
arguments are passed to the routines explicitly via command line or 
automatically via the menuing system.  Some of the routines are:
	logical and arithmetic operations on images that can be byte,
		short, int, float or complex.
	threshold, replace and offset operations.
	convert operations that can normalize and scale between bit,
		byte, short, int, and float.  Conversion from raw
		images to XVision images.
	dithering
	laser printer output (Imagen)
	FFT
	convolution (time domain and frequency domain)
	inverse and wiener filtering
	filter design
	histogram equalize and stretch
	expand and shrink
	spectral analysis
	statistics
	find tilt, remove tilt
	read and write image utilities that overcome byte order machine
		dependencies
	etc
	Add your favorite routine here

2.3   Plot Package.  A 2D/3D plotting package is integrated with the
menu system to provide a more complete image analysis package.  The
capabilities include:  2D, 3D, mesh and points-in-space plot types;
data input from image files, plot files, keyboard and user defined
function (this will allow you to generate an arbitrary function specified
by an equation, plot it, and then convert it to an image); rotation
and scaling of plots; multiple plots in multiple windows.

2.4  Display routine:  The display routine provides zoom, pan and detailed
inspection of images.  It also provides psuedocolor capabilities.  The display
routine allows multiple images with common color maps or independent
color maps.

2.5  Documentation (last but not least).  Every routine has a manual
page that is available via the menu help selection.  There are also
several tutorials to help you get started.  The source code is well
documented and will be provided.


3.  REQUIRED ENVIRONMENT
------------------------

This package has been tested on a microvax GPX running Ultrix 1.2, 
VaxStation 2000 running Ultrix 2.0, SUN 3/160C and a SUN 3/50M.  
We are currently using X window system V4R10 and have plans to port it
to V11.  We invite others to test XVision on different machines.


4.  FUTURE PLANS
----------------

We feel like we have just begun.  The highlights of things to come are:
metamenu - a semiautomatic system that installs new routines to XVision,
macros - a semiautomatic system to allow the user to write scripts or
image processing macros, interface to real time hardware and more
features in the plot package.  (And maybe fix some bugs along the way.)

rasure@hi.UUCP (John Rasure) (07/07/87)

The following describes how to obtain XVision.  The first part is
the standard licensing agreement that should be filled out and sent 
to the specified address.  The second part is a description of XVision.

XVision source will be sent to you on a 9-track tar tape along with
a set of manuals and other documentation.  We will begin sending 
copies on August 4th.

If you have questions, send them to:

	xvision@hc.dspo.gov
	{ucbvax,gatech,convex,pur-ee,lanl}unmvax!houdini!xvision


Note:  This is the first release of XVision, and we hope there will
be several more to come.  We decided to charge a distribution fee for
XVision so that we could maintain its quality and cover the costs
of providing it to the large number of people who have requested it.
We plan on using the Electronic mail addresses of the Licensees
to distribute additions and bug fixes.

************************************************************************


			SOFTWARE LICENSE AGREEMENT


  University of New Mexico, Department of Electrical and Computer Engineering


Agreement made this ________ day of ______________, 1987, between the
University of New Mexico acting though its Department of Electrical and
Computer Engineering (hereinafter referred to as the "EECE"), located in 
Albuquerque, New Mexico and

___________________________________________________________________________
an organization located in

___________________________________________________________________________
(hereinafter referred to as the "Licensee").


A.  LICENSE


1.  The EECE grants and the Licensee accepts, upon the terms and conditions
hereinafter set forth, a non-exclusive, non-transferable, and perpetual 
license to use the computer software system know as XVision Release 1.0 
(hereinafter referred to as the System), together with associated documentation.

2.  It is understood that the System is comprised of a number of software
components, some of which were authored and developed at institutions other
than the EECE.  Nothing in this Agreement is intended to supersede or reduce
the rights or obligations of the various institutions (hereinafter referred
to as the Sources) originating the components of the System.

B.  LICENSE FEE

1.  Upon execution of the Agreement, Licensee agrees to pay the EECE a 
distribution fee of $250.00, and a one-time license fee of $0.0.
All payments will be made by check or money order payable to Dept. of EECE, UNM;
and sent to XVision (Attn. Gladys Erickson), Department of Electrical and 
Computer Engineering, University of New Mexico, Albuquerque N.M. 87131.

2.  Upon acceptance of this Agreement by the EECE, the EECE agrees to deliver
to Licensee on machine-readable copy of the System, together with associated
documentation.

C.  USE RESTRICTIONS

1.  The Licensee agrees that neither the System or any of its components shall
be used as the basis of a commercial design tool product, and that it shall not 
be rewritten in another computer language or otherwise adapted to circumvent
the need for obtaining additional license rights.

2.  The license granted hereunder and the licensed System may not be assigned,
sublicensed, or otherwise transferred by the Licensee.  The Licensee shall
take reasonable precautions to ensure that neither the System or its
components are copied, transferred, or disclosed to parties other than the
Licensee.

3.  In no event shall the Licensee install or provide this System on any
computer system on which the Licensee purchases or sells computer-related
services.

4.  Nothing in this Agreement shall be construed as conferring rights to use
in advertising, publicity, or otherwise any trademark or the names of either
the EECE, the University of New Mexico, or any of the Sources.  Such use
requires prior approval in writing.

5.  Licensee is authorized to make one (1) copy of the system for back
up purposes.



D.  LIMITATION OF LIABILITY

1.  Neither the EECE nor the Sources make any warranties, either express or
implied, as to the condition of the System, its merchantability, or its
fitness for any particular purpose.  The Licensee agrees to accept the System
"as is" and it is understood that the EECE and Sources are not obligated to
provide maintenance, improvements, or support of any kind.

2.  The EECE and the Sources shall not be liable for any direct or 
consequential damages suffered by the Licensee or any other parties from the
use of the System.

3.  The Licensee agrees to indemnify the EECE for liability resulting from
the use of the System by Licensee.  The Licensee and the EECE each agree
to hold the other harmless for their own negligence.


E.  TITLE

1.  All intellectual property rights including, patent, copyright and 
trademark rights to the System are retained by the EECE and the Sources 
which authored the System.  The Licensee shall take all reasonable 
precautions to preserve these rights and do no acts in degradation of
these rights.

2.  The EECE and the Sources reserve the right to license or grant any other
rights to the System to other persons or entities.

3.  The System is the property of EECE and the Licensee has no rights
therein except as expressly printed herein.
				


F.  TERMINATION

1.  Subject to the provisions in 2. below, the Licensee and the EECE 
may mutually agree to terminate this Agreement at any time for any reason.

2.  In the event the EECE believes the Licensee has violated thee terms of
this Agreement, the EECE will inform the Licensee in writting of the possible
violation and the Licensee will have thirty (30) days from the date of such
notification to provide explanation or remedy satisfactory to the EECE.  The
Licensee agrees that if satisfactory explanation or remedy is not provided, 
the EECE may immediately terminate this Agreement.

3.  Licensee agrees that upon termination of this agreement it will return
the System to the Licenser or otherwise dispose of the System and its
copies as the Licenser instructs.


IN WITNESS WHEREOF, the parties hereto have executed this instrument as of the
dates given below:

University of New Mexico, Department of Electrical and Computer Engineering

	By    _____________________________________________

	Title _____________________________________________

	Date  _____________________________________________


	Licensee:

	By    _____________________________________________

	Title _____________________________________________

	Date  _____________________________________________

	Electronic Mail Address of Person who will 
	maintain the System: ______________________________

	___________________________________________________

	___________________________________________________


************************************************************************


The following contains a one page description of XVision. 

Outline
-------

1.  Overview
2.  Features
3.  System Requirements
4.  Future Plans


1.  OVERVIEW
------------

     XVision is a research and development tool designed to:
* facilitate investigation into new computer vision/image processing
  techniques and
* facilitate the development of turn key vision solutions for various
  application areas (automation, medicine, biology, astronomy, etc).

     XVision utilizes the X Window System, which provides a network
transparent windowing environment, and will soon be interfaced to
frame rate image processing hardware to provide the vision
programmer with a high-level, interactive vision system. 


2.  FEATURES
------------

2.1  Menuing system.  The menu system is based on Xmenu.  The menus
were designed to minimize the amount of user interaction; the
menus are reconfigured to reflect past actions and input from the
user.  The menu system controls all of the XVision capabilities and is
consistent from routine to routine.  As part of the menu system,
a command history is kept of the current session.  This history
can be used to build script files that can be used when an
interactive environment is not appropriate.

2.2  Image Processing Routines.  The routines are all separate C programs,
arguments are passed to the routines explicitly via command line or 
automatically via the menuing system.  Some of the routines are:
	logical and arithmetic operations on images that can be byte,
		short, int, float or complex.
	threshold, replace and offset operations.
	convert operations that can normalize and scale between bit,
		byte, short, int, and float.  Conversion from raw
		images to XVision images.
	dithering
	laser printer output (Imagen)
	FFT
	convolution (time domain and frequency domain)
	inverse and wiener filtering
	filter design
	histogram equalize and stretch
	expand and shrink
	spectral analysis
	statistics
	find tilt, remove tilt
	read and write image utilities that overcome byte order machine
		dependencies
	etc
	Add your favorite routine here

2.3   Plot Package.  A 2D/3D plotting package is integrated with the
menu system to provide a more complete image analysis package.  The
capabilities include:  2D, 3D, mesh and points-in-space plot types;
data input from image files, plot files, keyboard and user defined
function (this will allow you to generate an arbitrary function specified
by an equation, plot it, and then convert it to an image); rotation
and scaling of plots; multiple plots in multiple windows.

2.4  Display routine:  The display routine provides zoom, pan and detailed
inspection of images.  It also provides psuedocolor capabilities.  The display
routine allows multiple images with common color maps or independent
color maps.

2.5  Documentation (last but not least).  Every routine has a manual
page that is available via the menu help selection.  There are also
several tutorials to help you get started.  The source code is well
documented and will be provided.


3.  REQUIRED ENVIRONMENT
------------------------

This package has been tested on a microvax GPX running Ultrix 1.2, 
VaxStation 2000 running Ultrix 2.0, SUN 3/160C and a SUN 3/50M.  
We are currently using X window system V4R10 and have plans to port it
to V11.  We invite others to test XVision on different machines.


4.  FUTURE PLANS
----------------

We feel like we have just begun.  The highlights of things to come are:
metamenu - a semiautomatic system that installs new routines to XVision,
macros - a semiautomatic system to allow the user to write scripts or
image processing macros, interface to real time hardware and more
features in the plot package.  (And maybe fix some bugs along the way.)
-- 
Dr. John Rasure
Assistant Professor
University of New Mexico
Albuquerque, NM 87131
505-277-1351
NET-ADDRESS:	hi!houdini!rasure@hc.dspo.gov

weiser.pa@Xerox.COM.UUCP (07/07/87)

As a person with a bit of experience with licensing University software,
I find your license agreement to be a reasonably good one.  There are
three clauses that I object to, and I thought you might find these
comments useful:

The clause about not rewriting in another language is unduly restrictive
for a research product.  If the intent is to prevent circumventing the
license by a rewrite, then just say that.  But what if I want to make a
lisp version, or a C++ version, because that is what my research
demands? Perhaps you mean to handle rewrites on a case-by-case basis--if
so, I hope your intent is to say 'yes'.

The clause about indemnifying EECE is remininscent of the onerous
Berkeley license.  The University of Maryland, and many other places,
was unable to sign contracts requiring them to indemnify others.  Its
too bad to see this in here.  It will give you grief.

The business about a single back up copy is silly.  This is Unix, you
know.  People just do their normal backups, and that results in as many
copies as its results in on the backup tapes, and by making this
provision you make people suspicious that (a) you are not serious, (b)
you are making sure ALL of your licensee are in violation.  You don't
even restrict how many copies (non-backup) your licenses can make.  The
implication in the license is that you are offering a kind of SITE
license, and the holder can use the software on as many different
machines as they want as long as they are all theirs.  I think this is
good, this is the same way we did the Maryland software distribution.
But then why buy problems by making a single-copy-backup provision?

Hope you find these comments useful.

-mark