Difference: MDA (1 vs. 4)

Revision 42010-12-21 - MushfiqurRouf

Line: 1 to 1
 
META TOPICPARENT name="PsmSpace"

MDA

Line: 17 to 17
  To build MDA, cd to the MDA directory in which your version is downloaded, use tmk, and run tmk.
Changed:
<
<		To build MDA documentation, cd to the MDA/Doc directory and run "=tmk=".
>
>		To build MDA documentation, cd to the MDA/Doc directory and run tmk.
  All MDA development should happen in your own working copy. However, for reference, a copy of MDA exists at

Revision 32010-10-26 - MushfiqurRouf

Line: 1 to 1
 
META TOPICPARENT name="PsmSpace"

MDA

(This page is a work in progress...)

Changed:
<
<		This document provides README-level information about the MDA (Multi-Dimensional Array) package developed by Wolfgang Heidrich with contributions by members of the PSM Lab at UBC. It should probably remain relatively lightweight and should NOT contain information that would be better put in the MDA documentation itself. Ideally, MDA should be self-contained without this need for this wiki document.
>
>		This document provides README-level information about the MDA (Multi-Dimensional Array) package developed by Wolfgang Heidrich with contributions by members of the PSM Lab at UBC. It should probably remain relatively lightweight and should NOT contain information that would be better put in the MDA documentation itself. Ideally, MDA should be self-contained without this need for this wiki document.
 
Changed:
<
<		To obtain your own working copy of MDA on a machine on which dept file servers are mounted, use the following command.
>
>		To obtain your own working copy of MDA on a machine on which dept file servers are mounted, use the following command.
 
Changed:
<
<		svn co file:///ubc/cs/research/imager/project/psm/SVNRepository/MDA
>
>		svn co file:///ubc/cs/research/imager/project/psm/SVNRepository/MDA
 
Changed:
<
<		To obtain your own working copy of MDA on a machine with internet access on which dept file servers are NOT mounted, use the following command.
>
>		To obtain your own working copy of MDA on a machine with internet access on which dept file servers are NOT mounted, use the following command.
 
Changed:
<
<		svn co svn+ssh://username@okanagan.cs.ubc.ca/ubc/cs/research/imager/project/psm/SVNRepository/MDA
>
>		svn co svn+ssh://username@okanagan.cs.ubc.ca/ubc/cs/research/imager/project/psm/SVNRepository/MDA
 
Changed:
<
<		To build MDA, cd to the MDA directory in which your version is downloaded, and run "tmk".
>
>		To build MDA, cd to the MDA directory in which your version is downloaded, use tmk, and run tmk.
 
Changed:
<
<		To build MDA documentation, cd to the MDA/Doc directory and run "tmk".
>
>		To build MDA documentation, cd to the MDA/Doc directory and run "=tmk=".
 
Changed:
<
<		All MDA development should happen in your own working copy. However, for reference, a copy of MDA exists at
>
>		All MDA development should happen in your own working copy. However, for reference, a copy of MDA exists at
 
Changed:
<
<		/ubc/cs/research/imager/project/psm/MDA
>
>		/ubc/cs/research/imager/project/psm/MDA
 
Changed:
<
<		This version should be considered read-only and can be updated and rebuilt as desired. This version exists partly to provide a canonical place to obtain MDA documentation, at the following link.
>
>		This version should be considered read-only and can be updated and rebuilt as desired. This version exists partly to provide a canonical place to obtain MDA documentation, at the following link.
 
Changed:
<
<		file:///ubc/cs/research/imager/project/psm/MDA/Doc/SuSE_i586-10.3/html/index.html
>
>		file:///ubc/cs/research/imager/project/psm/MDA/Doc/SuSE_i586-10.3/html/index.html
 
Changed:
<
<		The above link will only work on machines with the CS dept netapp mounted because it uses a file: link, and it will only work if it is explicitly entered in the URL field of the browser. (I.e. just clicking on the above will not work on most browsers.) Should the documentation for MDA be located in a web-accessible directory (like the imager tech reports page) so that the above link can be modified to work from anywhere? That would make MDA Google-able, which may have various pros and cons...
>
>		The above link will only work on machines with the CS dept netapp mounted because it uses a file: link, and it will only work if it is explicitly entered in the URL field of the browser. (I.e. just clicking on the above will not work on most browsers.) Should the documentation for MDA be located in a web-accessible directory (like the imager tech reports page) so that the above link can be modified to work from anywhere? That would make MDA Google-able, which may have various pros and cons...
 

TODO

Changed:
<
<
  • Add MDA to the list of packages available with the "use" command.
>
>
  • Add MDA to the list of packages available with the "use" command.
 
  • Run a cron job every night that does an "svn update" and "tmk" in the reference copy directories mentioned above. (Optional.) This job should auto-email the PSM group if it fails to help ensure that the core checked-in version is always buildable.
Changed:
<
<
  • Should MDA documentation exist in the imager tech report web directory so it can be linked to from here?
  • Should some of the information on this page be put into a README file in the top-level MDA directory, and only be linked to in this page?
  • Should this TODO list be put into a TODO file in the top-level MDA directory, and only be linked to in this page?
  • Add a link to a complete set of all MDA SVN commits and their comment fields so we can get a history of all the changes that have been made.
  • List other proposed MDA development efforts here...
>
>
  • Should MDA documentation exist in the imager tech report web directory so it can be linked to from here?
  • Should some of the information on this page be put into a README file in the top-level MDA directory, and only be linked to in this page?
  • Should this TODO list be put into a TODO file in the top-level MDA directory, and only be linked to in this page?
  • Add a link to a complete set of all MDA SVN commits and their comment fields so we can get a history of all the changes that have been made.
  • List other proposed MDA development efforts here...
 

Raison d'être

Changed:
<
<		I put this document together to assemble some meta-information about MDA. As people enter and leave the lab, this document should provide (links to) the necessary background information about what MDA is and how to use it. It also provides a point of first contact to make it easy to get to the MDA documentation pages, or at least it will when I (or someone) gets these documentation links working.
>
>		I put this document together to assemble some meta-information about MDA. As people enter and leave the lab, this document should provide (links to) the necessary background information about what MDA is and how to use it. It also provides a point of first contact to make it easy to get to the MDA documentation pages, or at least it will when I (or someone) gets these documentation links working.
  -- AllanRempel - 13 Feb 2009

Revision 22009-02-17 - AllanRempel

Line: 1 to 1
 
META TOPICPARENT name="PsmSpace"

MDA

Changed:
<
<		(This page is a work in progress, which is why I haven't mentioned it yet... smile )
>
>		(This page is a work in progress...)
  This document provides README-level information about the MDA (Multi-Dimensional Array) package developed by Wolfgang Heidrich with contributions by members of the PSM Lab at UBC.
Changed:
<
<		It should NOT contain information that would be better put in the MDA documentation itself...
>
>		It should probably remain relatively lightweight and should NOT contain information that would be better put in the MDA documentation itself. Ideally, MDA should be self-contained without this need for this wiki document.
  To obtain your own working copy of MDA on a machine on which dept file servers are mounted, use the following command.
Line: 27 to 27
  file:///ubc/cs/research/imager/project/psm/MDA/Doc/SuSE_i586-10.3/html/index.html
Added:
>
>		The above link will only work on machines with the CS dept netapp mounted because it uses a file: link, and it will only work if it is explicitly entered in the URL field of the browser. (I.e. just clicking on the above will not work on most browsers.) Should the documentation for MDA be located in a web-accessible directory (like the imager tech reports page) so that the above link can be modified to work from anywhere? That would make MDA Google-able, which may have various pros and cons...
 

TODO

  • Add MDA to the list of packages available with the "use" command.
  • Run a cron job every night that does an "svn update" and "tmk" in the reference copy directories mentioned above. (Optional.) This job should auto-email the PSM group if it fails to help ensure that the core checked-in version is always buildable.
  • Should MDA documentation exist in the imager tech report web directory so it can be linked to from here?
Added:
>
>
  • Should some of the information on this page be put into a README file in the top-level MDA directory, and only be linked to in this page?
  • Should this TODO list be put into a TODO file in the top-level MDA directory, and only be linked to in this page?
  • Add a link to a complete set of all MDA SVN commits and their comment fields so we can get a history of all the changes that have been made.
 
  • List other proposed MDA development efforts here...

Raison d'être

Changed:
<
<		I put this document together to assemble some meta-information about MDA. As people enter and leave the lab, this document should provide the necessary background information about what MDA is and how to use it. It also provides a point of first contact to make it easy to get to the MDA documentation pages, or at least it will when I (or someone) gets these documentation links working.
>
>		I put this document together to assemble some meta-information about MDA. As people enter and leave the lab, this document should provide (links to) the necessary background information about what MDA is and how to use it. It also provides a point of first contact to make it easy to get to the MDA documentation pages, or at least it will when I (or someone) gets these documentation links working.
  -- AllanRempel - 13 Feb 2009

Revision 12009-02-13 - AllanRempel

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="PsmSpace"

MDA

(This page is a work in progress, which is why I haven't mentioned it yet... smile )

This document provides README-level information about the MDA (Multi-Dimensional Array) package developed by Wolfgang Heidrich with contributions by members of the PSM Lab at UBC. It should NOT contain information that would be better put in the MDA documentation itself...

To obtain your own working copy of MDA on a machine on which dept file servers are mounted, use the following command.

svn co file:///ubc/cs/research/imager/project/psm/SVNRepository/MDA

To obtain your own working copy of MDA on a machine with internet access on which dept file servers are NOT mounted, use the following command.

svn co svn+ssh://username@okanagan.cs.ubc.ca/ubc/cs/research/imager/project/psm/SVNRepository/MDA

To build MDA, cd to the MDA directory in which your version is downloaded, and run "tmk".

To build MDA documentation, cd to the MDA/Doc directory and run "tmk".

All MDA development should happen in your own working copy. However, for reference, a copy of MDA exists at

/ubc/cs/research/imager/project/psm/MDA

This version should be considered read-only and can be updated and rebuilt as desired. This version exists partly to provide a canonical place to obtain MDA documentation, at the following link.

file:///ubc/cs/research/imager/project/psm/MDA/Doc/SuSE_i586-10.3/html/index.html

TODO

  • Add MDA to the list of packages available with the "use" command.
  • Run a cron job every night that does an "svn update" and "tmk" in the reference copy directories mentioned above. (Optional.) This job should auto-email the PSM group if it fails to help ensure that the core checked-in version is always buildable.
  • Should MDA documentation exist in the imager tech report web directory so it can be linked to from here?
  • List other proposed MDA development efforts here...

Raison d'être

I put this document together to assemble some meta-information about MDA. As people enter and leave the lab, this document should provide the necessary background information about what MDA is and how to use it. It also provides a point of first contact to make it easy to get to the MDA documentation pages, or at least it will when I (or someone) gets these documentation links working.

-- AllanRempel - 13 Feb 2009

META FILEATTACHMENT attr="" comment="MDA Documentation" date="1234567293" name="index.html" path="index.html" size="405" user="agr" version="1.1"
View topic | History: r4 < r3 < r2 < r1 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback