5374297 718 718 19 5407038 11863636 11863637 11863638 11863639 33 2008-06-18 15:17:24.963 2010-04-22 23:43:13.393 5374313 5374315 5374323 5374347 5374349 5374351 5374362 5374364 5374366 5374372 5374374 5374375 5374377 5374379 5374397 5374399 5374400 5374401 5374424 5374426 5374427 5374429 5374430 5374700 5374702 5374704 5374705 5374707 11240144 11240190 11796544 11797041 5439530 5439531 19 717 718 691 692 693 694 695 696 697 698 699 700 701 702 703 704 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 4882436 4882437 4882438 4882439 4882440 4882441 4882442 5668949 5668950 5668951 5668952 5668953 5668954 5668955 5668956 5668957 11436145 11436146 11436147 11436148 11436149 11436150 19300570 2007-01-30 09:44:32.397 2010-03-31 14:19:34.883 global 720897 1]]> 11796998 2162701 718 5374085 2162701 19 11829752 3 2010-04-21 11:29:35.767 2010-04-21 11:40:48.027 11797002 11797003 11796990 2162701 718 5374085 2162701 19 11829744 1 2010-04-20 11:15:10.507 2010-04-20 11:15:10.507 2162700 19 2195467 1 2007-10-18 09:58:02.720 2007-10-18 09:58:02.720 5374220 2162702 11796533 19 5406964 14025117 14025118 17 2008-06-17 17:17:28.480 2010-08-02 13:09:31.253 5374246 5374249 5374251 5374279 5374281 9372188 10356023 11796727 11797020 11797030 11797042 11797044 11797046 11797163 12222521 13926688 2162705 19 2195472 1 2007-10-18 14:04:22.250 2007-10-18 14:04:22.250 5374197 2162701 718 5374085 2162701 19 5406944 13435023 13435024 13435025 13435026 13435027 26 2008-06-17 16:59:36.143 2010-06-09 17:57:16.467 5374199 5374200 5374203 5374218 5374269 6258707 9371792 9372312 9797766 9797767 10355194 10355718 10355721 10355969 11240176 11240182 11796530 11796583 11796587 11797031 13140014 13140016 13140018 13140019 13336610 5439505 10485897 13238273 11797304 718 718 19 11830048 13435008 13435009 13435010 16 2010-05-06 16:10:32.840 2010-06-09 14:41:59.267 12222472 12222478 12222479 12222482 12222484 12222486 12222487 12222488 12222491 12222518 12484723 12484725 13336596 13336598 13336600 12320772 11240565 718 718 19 11273291 11863465 32 2010-03-22 12:51:54.710 2010-04-15 14:21:02.773 11240568 11240571 11240572 11796500 11796501 11796502 11796503 11796505 11796507 11796510 11796511 11796512 11796514 11796515 11796516 11796517 11796518 11796519 11796520 11796521 11796717 11796718 11796720 11796741 11796798 11796800 11796801 11796804 11796806 11796896 11796904 11403389 11763729 6258689 2162701 718 5374085 2162701 19 6225922 7 2008-08-18 12:56:19.917 2009-08-17 16:22:15.243 6258691 6258694 6258695 6258697 6258699 10356014 6291457 6291458 6291459 6291460 917575 718 718 19 950342 3604626 14 2007-05-23 12:01:13.340 2008-12-17 10:12:31.010 917576 917578 917591 917592 1179758 1179988 1835012 1835013 5374286 5374288 5374289 8061024 8061026 11796533 5374220 718 5374220 19 11829299 1 2010-03-30 14:50:38.957 2010-03-30 14:50:38.957 5374146 2162701 718 5374085 2162701 19 5406895 13435021 13435022 59 2008-06-17 15:57:43.497 2010-06-09 17:52:39.507 5374155 5374157 5374159 5374161 5374162 5374201 5374263 5374710 5374711 6258993 6259074 6259077 6259080 9371784 9371798 9371800 9372311 10355106 10355216 10355218 10355219 10355220 10355221 10355222 10355224 10355225 10355226 10355227 10355228 10355229 10355230 10355231 10355233 10355299 10355500 10355508 10355713 10355714 10355961 10355964 10355967 10355992 11240173 11240179 11796493 11796494 11796527 11796581 11796585 11796589 11797033 12222519 12484621 13336584 13336585 13336587 13336595 13336608 5374142 2162701 718 5374085 2162701 19 5406891 13729983 13729984 13729985 13729986 13729987 13729988 13729989 13729990 13729991 13729992 43 2008-06-17 15:56:12.620 2010-06-22 17:03:51.547 5374143 5374148 5374163 5374164 5374165 5374202 6258700 6258726 6259063 6259072 9371786 9371789 9371802 10355502 10355506 10355510 10355511 10355512 10355715 10355745 10355747 10355751 10355753 10355754 10355963 10355965 10355995 10355997 10355998 11240174 11240181 11796528 11796586 11796588 11796594 11797032 11797195 11797196 11797198 12222489 12222523 13664378 5374151 2162701 718 5374085 2162701 19 5406899 12714560 12714561 12714562 12714563 12714564 12714565 12714566 12714567 12714568 12714569 12714570 75 2008-06-17 16:00:47.667 2010-05-26 19:01:34.040 5374171 5374173 5374176 5374181 5374186 5374190 5374213 5374264 5374271 5374273 5374274 5374276 5374326 5374328 5374331 5374333 5374408 6258704 6259076 6259078 6259087 6259089 10355236 10355237 10355723 10355725 10355727 10355743 11240168 11240171 11240178 11240184 11240186 11240187 11796508 11796523 11796525 11796531 11796577 11796580 11796591 11796592 11796593 11797036 11797038 12484703 12484705 12484708 12484710 12484712 12484714 12484716 12484718 12484720 12484726 12484729 12484731 12484733 12484734 12484741 12484743 12484745 12484747 12484748 12484750 12484754 12484756 12484757 12484759 12484760 12484761 12484763 12484764 12484766 927 718 718 19 924 9899832 9899833 9899834 9899835 4620298 18 2007-02-21 13:30:57.423 2009-05-12 10:30:36.037 930 963 964 1179812 1179813 1835036 1835037 1835038 1835039 1835040 1835052 2162939 9798419 9798420 9798422 9798437 9798439 35 41 2031617 2031620 2031621 2031618 2031619 9928762 6258712 2162701 718 5374085 2162701 19 6225941 12288211 12288212 12288213 12288214 12288215 12288216 12288217 12288218 32 2008-08-18 17:36:24.903 2010-05-12 15:14:48.480 6258715 6258717 6258719 6258721 6258722 6258723 6258724 6258729 6258731 6258733 6258735 6259059 6259060 6259065 6259067 6259070 9371788 9371790 9371804 10355505 10355716 10355993 11240175 11240180 11796529 11796582 11796584 11796590 11796595 11797034 12222520 5374134 2162701 718 5374085 2162701 19 5406883 13205714 13205715 13205716 13205717 13205718 13205719 37 2008-06-17 15:47:42.157 2010-06-02 14:49:17.730 5374136 5374138 5374147 5374232 5374234 9371782 9372339 10355102 10355104 10355105 10355111 10355113 10355300 10355301 10355710 10355711 11240055 11240056 11240057 11240058 11240060 11240061 11240062 11796486 11796488 11796490 11796578 11796579 11797176 11797177 11797187 11797189 11797191 13140034 13140035 13140037 5374109 19 5406859 3 2008-06-17 14:21:54.363 2010-06-09 15:44:46.257 11796540 13336603 32797 theme.key com.atlassian.confluence.themes.leftnavigation:leftnavigation ]]> 32798 AVED false global ]]> 5374092 19 5406844 11862116 11862117 11862118 11862119 8 2008-06-17 13:47:41.367 2010-03-30 14:53:43.033 5374094 5374100 5374103 5374217 5374257 11796537 11796538 11240197 19 11272938 4 2010-03-01 22:44:57.320 2013-05-28 15:28:42.737 11240199 11240216 21364783 5374105 19 5406856 13205720 10 2008-06-17 14:20:48.653 2010-06-02 14:51:47.860 5374107 5374111 5374152 5374153 6259357 11796539 11796725 11796726 13140039 11240205 2162701 718 5374085 2162701 19 11272945 13435032 13435033 71 2010-03-01 22:54:03.393 2010-06-09 23:15:27.627 11240208 11240210 11240212 11240214 11240217 11240222 11240224 11796575 11796603 11796605 11796607 11796716 11796742 11796745 11796746 11796747 11796749 11796751 11796752 11796753 11796754 11796756 11796757 11796758 11796759 11796761 11796763 11796764 11796765 11796766 11796767 11796769 11796771 11796772 11796774 11796776 11796778 11796780 11796783 11796786 11796788 11796789 11796854 11796870 11796873 11796878 11796880 11796882 11796891 11796906 11796988 11796992 11796996 11797000 11797004 11797005 11797006 11797008 11797010 11797179 11797183 11797185 11797294 12484706 13336589 13336590 13336591 13336611 13336613 13336614 2162702 5374220 718 5374220 19 2195469 12288126 12288127 12288128 12288129 12288130 12288131 12288132 12288133 12288134 12288135 12288136 12288137 12288138 12288139 12288140 12288141 12288142 12288143 12288144 12288145 12288146 12288147 12288148 12288149 12288150 12288151 12288152 12288153 12288154 12288155 12288156 12288157 12288158 12288159 12288160 12288161 12288162 12288163 12288164 12288165 12288166 12288167 12288168 12288169 12288170 12288171 12288172 12288173 12288174 12288175 12288176 12288177 12288178 12288179 12288180 12288181 12288182 12288183 12288184 12288185 12288186 12288187 12288188 43 2007-10-18 09:59:49.230 2010-05-11 14:49:54.200 2162720 2162722 2162727 2162728 2162729 2162730 2162731 2162732 2162733 2162734 2162735 2162736 2162737 2162738 2162739 2162740 2162741 2162742 2162751 5374183 5374191 5374205 5374214 5374244 5374247 5374283 5374418 5374420 5374422 6946829 6946831 9798537 10355546 10355553 10355554 10356024 10911986 10912021 10912062 11796728 12222498 12222500 5374085 2162701 19 5406839 11862259 11862260 11 2008-06-17 13:36:40.310 2010-03-31 14:20:21.303 5374089 5374096 5374209 5374215 5374223 11240142 11240188 11796536 11796541 11796574 2162701 5374085 5374134 5374142 5374146 5374151 5374197 6258689 6258712 11240205 11796990 11796998 718 5374085 19 2195468 14614778 14614779 14614780 14614781 14614782 14614783 14614784 14614785 4620297 104 2007-10-18 09:59:11.053 2010-08-30 15:15:40.010 2162709 2162710 2162711 2162712 2162713 2162714 2162715 2162716 2162717 2162718 2162719 2162723 2162724 2162743 2162744 2162745 2162746 2162747 2162748 2162754 2162778 2162779 2162780 2162781 2162782 2162783 2162784 2162785 2162786 2162787 2162788 2162789 2162790 2162791 2162792 2162793 2162811 2162812 2162813 2162830 2162831 2162832 2162833 2162841 5374113 5374116 5374118 5374121 5374123 5374124 5374126 5374128 5374130 5374132 5374135 5374140 5374144 5374149 5374167 5374169 5374259 5374260 5374261 5374262 5374266 5374267 5374325 5374404 6258702 6258713 6258728 6259068 10355242 10355503 10355729 10355994 11240146 11240177 11240183 11240192 11240206 11240220 11240223 11796526 11796545 11796549 11796550 11796568 11796570 11796598 11796602 11796714 11796872 11796875 11797035 11797193 11797194 12222480 12222522 12484713 13336601 13664374 14516268 718 927 917575 5374297 11240565 11797304 19 715 21430386 21430387 21430388 21430389 21430390 21430391 21430392 21430393 21430394 21430395 3604525 83 2007-01-30 09:44:32.403 2013-05-28 15:29:12.267 905 906 907 917572 917573 917574 917577 917579 917580 917589 917590 1179656 2162845 2162846 2162847 2162940 5374078 5374080 5374081 5374112 5374227 5374228 5374230 5374231 5374238 5374239 5374240 5374242 5374255 5374278 5374717 8356120 8356123 8356126 9798421 9798436 9798438 10912207 10912271 11240051 11240143 11240147 11240149 11240189 11240194 11240201 11240202 11240203 11240218 11240535 11240537 11240543 11240545 11240563 11240567 11240569 11240579 11240580 11240581 11240612 11796543 11796573 11796609 11796719 11796721 11796722 11796894 11796895 11796898 11796900 11796902 11796963 11796965 11796966 11796970 11797026 11797040 11797299 12222516 13926699 15204367 21364784 11403385 11403386 11403387 11403388 2162725 19 2195492 5505945 5505946 5505947 5505948 5505949 5505950 5505951 51 2007-10-18 16:43:05.903 2008-06-18 11:33:22.517 2162726 2162749 2162750 2162752 2162753 2162755 2162756 2162757 2162758 2162759 2162760 2162761 2162762 2162763 2162764 2162765 2162766 2162767 2162768 2162769 2162770 2162771 2162772 2162773 2162774 2162775 2162776 2162777 2162794 2162795 2162796 2162797 2162798 2162799 2162800 2162801 2162802 2162803 2162804 2162805 2162806 2162807 2162808 2162809 2162810 2162814 2162815 5374206 5374212 5374282 21430392 718 2013-05-28 15:29:12.353 2013-05-28 15:29:12.353 21430393 718 2013-05-28 15:29:12.353 2013-05-28 15:29:12.353 21430394 718 2013-05-28 15:29:12.353 2013-05-28 15:29:12.353 21430395 718 2013-05-28 15:29:12.353 2013-05-28 15:29:12.353 21430388 718 2013-05-28 15:29:12.353 2013-05-28 15:29:12.353 21430389 718 2013-05-28 15:29:12.353 2013-05-28 15:29:12.353 21430390 718 2013-05-28 15:29:12.353 2013-05-28 15:29:12.353 21430391 718 2013-05-28 15:29:12.353 2013-05-28 15:29:12.353 10912207 10944962 38 2007-01-30 09:44:32.403 2009-05-12 10:30:36.017 718 11796965 11829719 73 2007-01-30 09:44:32.403 2010-04-16 14:08:15.027 718 11796966 11829720 74 2007-01-30 09:44:32.403 2010-04-16 14:08:56.960 718 11796963 11829717 72 2007-01-30 09:44:32.403 2010-04-15 14:12:22.190 718 11796970 11829724 75 2007-01-30 09:44:32.403 2010-04-16 14:13:52.293 718 950342 917575 11796854 11829612 43 2010-03-01 22:54:03.393 2010-04-14 12:12:52.283 11240205 11796872 11829630 93 2007-10-18 09:59:11.053 2010-04-13 13:08:49.750 2162701 11796873 11829631 45 2010-03-01 22:54:03.393 2010-04-15 11:17:53.767 11240205 11796870 11829628 44 2010-03-01 22:54:03.393 2010-04-15 10:43:51.787 11240205 11796882 11829640 48 2010-03-01 22:54:03.393 2010-04-15 11:28:15.910 11240205 11796880 11829638 47 2010-03-01 22:54:03.393 2010-04-15 11:27:06.827 11240205 11796878 11829636 46 2010-03-01 22:54:03.393 2010-04-15 11:18:45.953 11240205 11796875 11829633 94 2007-10-18 09:59:11.053 2010-04-15 11:18:45.790 2162701 11796906 11829661 50 2010-03-01 22:54:03.393 2010-04-15 12:15:35.947 11240205 11796904 11829659 31 2010-03-22 12:51:54.710 2010-04-15 14:10:15.343 11240565 11796902 11829657 71 2007-01-30 09:44:32.403 2010-04-15 14:11:24.123 718 11796900 11829656 70 2007-01-30 09:44:32.403 2010-04-15 14:10:45.293 718 11796898 11829655 69 2007-01-30 09:44:32.403 2010-04-15 14:10:15.317 718 11796895 11829653 68 2007-01-30 09:44:32.403 2010-04-15 14:09:50.213 718 6291457 6258689 2008-08-18 13:04:11.510 2008-08-18 13:05:50.313 22378 3 11796896 11829654 30 2010-03-22 12:51:54.710 2010-04-14 16:41:03.453 11240565 6291459 6258689 2008-08-18 13:04:11.510 2008-08-18 13:05:35.207 22378 2 6291457 11796894 11829652 67 2007-01-30 09:44:32.403 2010-04-13 13:18:31.377 718 6291458 6258689 2008-08-18 13:04:11.510 2008-08-18 13:04:11.510 23673 1 6291457 11796891 11829649 49 2010-03-01 22:54:03.393 2010-04-15 11:31:53.393 11240205 6291460 6258689 2008-08-18 13:36:58.923 2008-08-18 13:36:58.923 10457 1 12288217 6258712 2010-05-12 15:14:48.517 2010-05-12 15:14:48.517 12288216 6258712 2010-05-12 15:14:48.517 2010-05-12 15:14:48.517 11796780 11829537 38 2010-03-01 22:54:03.393 2010-04-14 11:42:37.407 11240205 12288218 6258712 2010-05-12 15:14:48.517 2010-05-12 15:14:48.517 12288213 6258712 2010-05-12 15:14:48.517 2010-05-12 15:14:48.517 11796783 11829540 39 2010-03-01 22:54:03.393 2010-04-14 11:57:18.707 11240205 12288212 6258712 2010-05-12 15:14:48.517 2010-05-12 15:14:48.517 12288215 6258712 2010-05-12 15:14:48.517 2010-05-12 15:14:48.517 12288214 6258712 2010-05-12 15:14:48.517 2010-05-12 15:14:48.517 11796786 11829543 40 2010-03-01 22:54:03.393 2010-04-14 12:01:26.717 11240205 11796788 11829545 41 2010-03-01 22:54:03.393 2010-04-14 12:03:44.630 11240205 11796789 11829546 42 2010-03-01 22:54:03.393 2010-04-14 12:09:16.677 11240205 11796798 11829555 25 2010-03-22 12:51:54.710 2010-04-14 10:28:45.500 11240565 10912062 10944821 39 2007-10-18 09:59:49.230 2009-11-09 11:38:31.200 2162702 11796800 11829557 26 2010-03-22 12:51:54.710 2010-04-14 13:18:57.840 11240565 11796801 11829558 27 2010-03-22 12:51:54.710 2010-04-14 13:38:30.947 11240565 11796804 11829561 28 2010-03-22 12:51:54.710 2010-04-14 13:39:18.257 11240565 11796806 11829563 29 2010-03-22 12:51:54.710 2010-04-14 16:39:31.360 11240565 12288187 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 12288186 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 12288185 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 12288184 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 12288183 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 12288182 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 12288181 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 12288180 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 12288188 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 12288211 6258712 2010-05-12 15:14:48.517 2010-05-12 15:14:48.517 11796719 11829476 64 2007-01-30 09:44:32.403 2010-03-31 14:45:00.007 718 11240171 11272913 30 2008-06-17 16:00:47.667 2010-03-01 16:53:06.187 5374151 12288149 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11796720 11829477 23 2010-03-22 12:51:54.710 2010-04-13 13:12:32.263 11240565 12288148 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11796721 11829478 65 2007-01-30 09:44:32.403 2010-04-13 13:16:43.470 718 11240173 11272915 43 2008-06-17 15:57:43.497 2009-08-14 17:49:39.150 5374146 12288151 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11796722 11829479 66 2007-01-30 09:44:32.403 2010-04-13 13:17:19.097 718 11240174 11272916 30 2008-06-17 15:56:12.620 2009-08-14 18:54:04.640 5374142 12288150 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240175 11272917 23 2008-08-18 17:36:24.903 2009-08-14 17:49:39.227 6258712 12288153 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 10911986 10944748 37 2007-10-18 09:59:49.230 2009-08-19 11:20:34.200 2162702 11240176 11272918 15 2008-06-17 16:59:36.143 2009-08-13 18:40:40.500 5374197 11796716 11829473 12 2010-03-01 22:54:03.393 2010-03-31 14:42:46.367 11240205 12288152 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240177 11272919 78 2007-10-18 09:59:11.053 2010-03-01 10:52:31.703 2162701 11796717 11829474 21 2010-03-22 12:51:54.710 2010-03-30 14:38:31.997 11240565 12288155 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11796718 11829475 22 2010-03-22 12:51:54.710 2010-04-13 13:12:07.600 11240565 11240178 11272920 31 2008-06-17 16:00:47.667 2010-03-01 22:12:34.820 5374151 12288154 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240179 11272921 44 2008-06-17 15:57:43.497 2010-03-01 22:20:15.837 5374146 11796727 11829484 8 2008-06-17 17:17:28.480 2009-08-19 11:19:47.043 5374220 12288157 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11796728 11829485 40 2007-10-18 09:59:49.230 2009-11-12 09:41:46.103 2162702 11240180 11272922 24 2008-08-18 17:36:24.903 2010-03-01 22:20:15.950 6258712 12288156 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240181 11272923 31 2008-06-17 15:56:12.620 2010-03-01 22:20:15.910 5374142 12288159 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240182 11272924 16 2008-06-17 16:59:36.143 2010-03-01 22:20:15.990 5374197 12288158 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240183 11272925 79 2007-10-18 09:59:11.053 2010-03-01 22:20:16.013 2162701 12288161 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240184 11272926 32 2008-06-17 16:00:47.667 2010-03-01 22:20:16.063 5374151 12288160 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11796725 11829482 7 2008-06-17 14:20:48.653 2010-03-30 14:53:43.043 5374105 12288163 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240186 11272928 33 2008-06-17 16:00:47.667 2010-03-01 22:20:57.613 5374151 11796726 11829483 8 2008-06-17 14:20:48.653 2010-04-13 13:19:49.977 5374105 12288162 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240188 11272930 7 2008-06-17 13:36:40.310 2010-03-01 10:52:31.523 5374085 12288164 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240187 11272929 34 2008-06-17 16:00:47.667 2010-03-01 22:23:13.140 5374151 12288165 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240190 11272932 30 2008-06-18 15:17:24.963 2010-03-01 10:52:31.627 5374297 12288166 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240189 11272931 44 2007-01-30 09:44:32.403 2010-03-01 10:58:42.627 718 12288167 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 21430386 718 2013-05-28 15:29:12.353 2013-05-28 15:29:12.353 11240192 11272934 80 2007-10-18 09:59:11.053 2010-03-01 22:20:57.567 2162701 12288168 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 21430387 718 2013-05-28 15:29:12.353 2013-05-28 15:29:12.353 12288169 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240194 11272936 45 2007-01-30 09:44:32.403 2010-03-01 22:23:45.537 718 12288170 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 12288171 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 12288172 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 12288173 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 11796746 11829503 15 2010-03-01 22:54:03.393 2010-04-14 10:34:31.067 11240205 12288174 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 11796745 11829502 14 2010-03-01 22:54:03.393 2010-04-14 10:30:46.977 11240205 12288175 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 12288176 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 11240199 11272940 1 2010-03-01 22:44:57.320 2010-03-01 22:44:57.320 11240197 12288177 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 11240202 11272943 47 2007-01-30 09:44:32.403 2010-03-01 22:49:12.757 718 11796742 11829499 13 2010-03-01 22:54:03.393 2010-04-13 13:11:06.837 11240205 12288178 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 11240201 11272942 46 2007-01-30 09:44:32.403 2010-03-01 22:44:06.027 718 11796741 11829498 24 2010-03-22 12:51:54.710 2010-04-13 13:16:43.507 11240565 12288179 2162702 2010-05-11 14:49:54.233 2010-05-11 14:49:54.233 11796753 11829510 20 2010-03-01 22:54:03.393 2010-04-14 10:45:54.157 11240205 11240206 11272946 81 2007-10-18 09:59:11.053 2010-03-01 22:23:45.733 2162701 11863465 11240565 2010-04-15 14:21:02.797 2010-04-15 14:21:02.797 11796754 11829511 21 2010-03-01 22:54:03.393 2010-04-14 10:47:00.373 11240205 11240203 11272944 48 2007-01-30 09:44:32.403 2010-03-01 22:49:32.343 718 11796751 11829508 18 2010-03-01 22:54:03.393 2010-04-14 10:39:13.517 11240205 11796752 11829509 19 2010-03-01 22:54:03.393 2010-04-14 10:45:08.337 11240205 11796749 11829506 17 2010-03-01 22:54:03.393 2010-04-14 10:36:04.930 11240205 11240210 11272950 2 2010-03-01 22:54:03.393 2010-03-01 23:02:44.037 11240205 11796747 11829504 16 2010-03-01 22:54:03.393 2010-04-14 10:35:12.657 11240205 11240208 11272948 1 2010-03-01 22:54:03.393 2010-03-01 22:54:03.393 11240205 11796761 11829518 26 2010-03-01 22:54:03.393 2010-04-14 11:25:56.810 11240205 12288127 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240214 11272954 4 2010-03-01 22:54:03.393 2010-03-01 23:25:51.707 11240205 12288126 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 10912021 10944783 38 2007-10-18 09:59:49.230 2009-11-05 11:08:31.560 2162702 11796759 11829516 25 2010-03-01 22:54:03.393 2010-04-14 11:12:48.270 11240205 11240212 11272952 3 2010-03-01 22:54:03.393 2010-03-01 23:06:12.853 11240205 11240217 11272957 5 2010-03-01 22:54:03.393 2010-03-01 23:29:44.990 11240205 11796757 11829514 23 2010-03-01 22:54:03.393 2010-04-14 11:00:53.050 11240205 12288131 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240218 11272958 49 2007-01-30 09:44:32.403 2010-03-01 22:49:56.100 718 11796758 11829515 24 2010-03-01 22:54:03.393 2010-04-14 11:10:15.807 11240205 12288130 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 12288129 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240216 11272956 2 2010-03-01 22:44:57.320 2010-03-01 22:46:57.357 11240197 11796756 11829513 22 2010-03-01 22:54:03.393 2010-04-14 10:47:49.390 11240205 12288128 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240222 11272962 6 2010-03-01 22:54:03.393 2010-03-01 23:33:44.070 11240205 12288134 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11796769 11829526 32 2010-03-01 22:54:03.393 2010-04-14 11:33:10.990 11240205 12288135 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240220 11272960 82 2007-10-18 09:59:11.053 2010-03-01 22:55:57.120 2162701 12288132 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11796767 11829524 31 2010-03-01 22:54:03.393 2010-04-14 11:32:56.177 11240205 12288133 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11796766 11829523 30 2010-03-01 22:54:03.393 2010-04-14 11:32:30.207 11240205 12288138 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11796765 11829522 29 2010-03-01 22:54:03.393 2010-04-14 11:31:56.660 11240205 12288139 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240224 11272964 7 2010-03-01 22:54:03.393 2010-03-01 23:44:29.407 11240205 11796764 11829521 28 2010-03-01 22:54:03.393 2010-04-14 11:30:34.820 11240205 12288136 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11240223 11272963 83 2007-10-18 09:59:11.053 2010-03-01 23:39:38.777 2162701 11796763 11829520 27 2010-03-01 22:54:03.393 2010-04-14 11:28:26.323 11240205 12288137 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11796778 11829535 37 2010-03-01 22:54:03.393 2010-04-14 11:38:54.313 11240205 12288142 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 12288143 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11796776 11829533 36 2010-03-01 22:54:03.393 2010-04-14 11:37:27.243 11240205 12288140 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 12288141 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11796774 11829531 35 2010-03-01 22:54:03.393 2010-04-14 11:36:31.550 11240205 12288146 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 12288147 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 12288144 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11796772 11829529 34 2010-03-01 22:54:03.393 2010-04-14 11:36:10.027 11240205 12288145 2162702 2010-05-11 14:49:54.230 2010-05-11 14:49:54.230 11796771 11829528 33 2010-03-01 22:54:03.393 2010-04-14 11:34:14.440 11240205 5439531 5374297 2008-07-01 16:04:47.610 2008-07-01 16:04:47.610 1837886 1 5439530 5374297 2008-07-01 16:02:40.467 2008-07-01 16:02:40.467 2913521 1 11240168 11272910 29 2008-06-17 16:00:47.667 2009-08-06 15:01:29.090 5374151 5439505 5374197 2008-06-17 17:04:11.990 2008-06-17 17:04:11.990 37410 1 11796714 11829471 92 2007-10-18 09:59:11.053 2010-03-31 14:31:13.417 2162701 11240147 11272891 42 2007-01-30 09:44:32.403 2010-03-01 10:52:31.567 718 11240149 11272893 43 2007-01-30 09:44:32.403 2010-03-01 10:56:10.547 718 11240144 11272888 29 2008-06-18 15:17:24.963 2008-07-01 16:13:15.940 5374297 11240143 11272887 41 2007-01-30 09:44:32.403 2010-02-23 11:09:17.557 718 11240146 11272890 77 2007-10-18 09:59:11.053 2009-08-14 17:49:39.267 2162701 11240142 11272886 6 2008-06-17 13:36:40.310 2008-06-17 17:18:34.093 5374085 11240061 11272808 22 2008-06-17 15:47:42.157 2010-02-23 11:28:03.870 5374134 11796609 11829368 63 2007-01-30 09:44:32.403 2010-03-31 14:20:01.687 718 11240062 11272809 23 2008-06-17 15:47:42.157 2010-02-23 11:28:22.503 5374134 11796607 11829366 11 2010-03-01 22:54:03.393 2010-03-31 14:41:46.297 11240205 11240060 11272807 21 2008-06-17 15:47:42.157 2010-02-23 11:25:28.027 5374134 11796605 11829364 10 2010-03-01 22:54:03.393 2010-03-31 14:40:52.207 11240205 11796603 11829362 9 2010-03-01 22:54:03.393 2010-03-31 14:21:05.277 11240205 11796602 11829361 91 2007-10-18 09:59:11.053 2010-03-31 14:29:39.537 2162701 11240051 11272798 40 2007-01-30 09:44:32.403 2010-01-04 13:30:24.670 718 11240058 11272805 20 2008-06-17 15:47:42.157 2010-02-23 11:25:13.780 5374134 11796598 11829359 90 2007-10-18 09:59:11.053 2010-03-31 14:18:40.650 2162701 11240057 11272804 19 2008-06-17 15:47:42.157 2010-02-23 11:24:41.540 5374134 11240056 11272803 18 2008-06-17 15:47:42.157 2010-02-23 11:23:50.050 5374134 11240055 11272802 17 2008-06-17 15:47:42.157 2009-08-05 15:18:52.230 5374134 11796595 11829357 29 2008-08-18 17:36:24.903 2010-03-31 14:24:47.873 6258712 11796594 11829356 35 2008-06-17 15:56:12.620 2010-03-31 14:24:47.813 5374142 13336584 13369352 54 2008-06-17 15:57:43.497 2010-05-13 16:24:18.773 5374146 11796593 11829355 43 2008-06-17 16:00:47.667 2010-03-31 14:25:08.677 5374151 11796592 11829354 42 2008-06-17 16:00:47.667 2010-03-31 14:24:47.897 5374151 11796591 11829353 41 2008-06-17 16:00:47.667 2010-03-31 14:23:28.457 5374151 13336585 13369353 55 2008-06-17 15:57:43.497 2010-06-09 13:09:21.840 5374146 11796590 11829352 28 2008-08-18 17:36:24.903 2010-03-31 14:24:26.850 6258712 11796589 11829351 50 2008-06-17 15:57:43.497 2010-03-31 14:24:26.910 5374146 11796588 11829350 34 2008-06-17 15:56:12.620 2010-03-31 14:24:26.953 5374142 11796587 11829349 19 2008-06-17 16:59:36.143 2010-03-31 14:24:01.107 5374197 13336591 13369359 67 2010-03-01 22:54:03.393 2010-06-09 13:59:43.540 11240205 13336589 13369357 65 2010-03-01 22:54:03.393 2010-05-25 16:00:09.750 11240205 13336590 13369358 66 2010-03-01 22:54:03.393 2010-06-09 13:47:11.247 11240205 13336587 13369355 56 2008-06-17 15:57:43.497 2010-06-09 13:14:39.470 5374146 6225922 6258689 13336601 13369369 101 2007-10-18 09:59:11.053 2010-05-25 20:53:54.440 2162701 13336600 13369368 15 2010-05-06 16:10:32.840 2010-06-09 14:40:07.887 11797304 13336598 13369366 14 2010-05-06 16:10:32.840 2010-06-09 14:39:19.530 11797304 13336595 13369363 57 2008-06-17 15:57:43.497 2010-06-09 13:18:19.027 5374146 13336596 13369364 13 2010-05-06 16:10:32.840 2010-05-25 21:33:48.323 11797304 13336610 13369378 25 2008-06-17 16:59:36.143 2010-05-27 16:52:24.390 5374197 13238273 5374197 2010-05-27 16:47:36.783 2010-05-27 16:47:36.783 2279150 1 13336608 13369376 58 2008-06-17 15:57:43.497 2010-06-09 14:28:21.180 5374146 13336603 13369371 2 2008-06-17 14:21:54.363 2010-03-30 14:54:03.290 5374109 13336614 13369382 70 2010-03-01 22:54:03.393 2010-06-09 23:14:38.497 11240205 13336613 13369381 69 2010-03-01 22:54:03.393 2010-06-09 20:49:39.390 11240205 13336611 13369379 68 2010-03-01 22:54:03.393 2010-06-09 14:05:02.263 11240205 11796541 11829307 9 2008-06-17 13:36:40.310 2010-03-30 14:53:16.230 5374085 11796540 11829306 1 2008-06-17 14:21:54.363 2008-06-18 11:34:22.460 5374109 11796539 11829305 6 2008-06-17 14:20:48.653 2008-10-16 12:39:09.003 5374105 11796545 11829310 85 2007-10-18 09:59:11.053 2010-03-30 14:48:39.370 2162701 11796544 11829309 31 2008-06-18 15:17:24.963 2010-03-01 22:23:45.627 5374297 5374717 5407448 31 2007-01-30 09:44:32.403 2008-06-18 11:01:12.573 718 11796543 11829308 61 2007-01-30 09:44:32.403 2010-03-25 11:52:04.183 718 11796550 11829313 87 2007-10-18 09:59:11.053 2010-03-30 15:14:18.210 2162701 11796549 11829312 86 2007-10-18 09:59:11.053 2010-03-30 14:54:51.317 2162701 3604525 11 718 2008-04-17 15:03:15.030 2008-05-30 15:44:15.043 11796525 11829292 37 2008-06-17 16:00:47.667 2010-03-30 14:40:21.893 5374151 5374704 5407435 26 2008-06-18 15:17:24.963 2008-07-01 16:07:37.437 5374297 917573 950340 5 2007-01-30 09:44:32.403 2007-05-23 11:39:13.340 718 11796526 11829293 84 2007-10-18 09:59:11.053 2010-03-01 23:44:47.843 2162701 917574 950341 6 2007-01-30 09:44:32.403 2007-05-23 11:42:38.740 718 11796523 11829290 36 2008-06-17 16:00:47.667 2010-03-30 14:19:05.713 5374151 5374705 5407436 27 2008-06-18 15:17:24.963 2008-07-01 16:11:39.867 5374297 917572 950339 4 2007-01-30 09:44:32.403 2007-02-14 14:58:23.510 718 11796529 11829296 25 2008-08-18 17:36:24.903 2010-03-01 22:20:57.513 6258712 5374700 5407431 24 2008-06-18 15:17:24.963 2008-06-24 12:35:53.907 5374297 917577 950344 7 2007-01-30 09:44:32.403 2007-05-23 11:43:06.400 718 11796530 11829297 17 2008-06-17 16:59:36.143 2010-03-01 22:20:57.557 5374197 917578 950345 2 2007-05-23 12:01:13.340 2007-05-23 12:40:12.347 917575 5374702 5407433 25 2008-06-18 15:17:24.963 2008-07-01 16:06:15.207 5374297 11796527 11829294 47 2008-06-17 15:57:43.497 2010-03-30 13:13:02.563 5374146 11796528 11829295 32 2008-06-17 15:56:12.620 2010-03-01 22:20:57.537 5374142 917576 950343 1 2007-05-23 12:01:13.340 2007-05-23 12:01:13.340 917575 5374711 5407442 9 2008-06-17 15:57:43.497 2008-07-03 12:45:07.263 5374146 11796531 11829298 38 2008-06-17 16:00:47.667 2010-03-30 14:47:31.447 5374151 11796537 11829303 6 2008-06-17 13:47:41.367 2008-06-18 11:32:53.300 5374092 11796538 11829304 7 2008-06-17 13:47:41.367 2010-03-30 14:53:16.270 5374092 5374707 5407438 28 2008-06-18 15:17:24.963 2008-07-01 16:11:58.837 5374297 11273291 11240565 5374710 5407441 8 2008-06-17 15:57:43.497 2008-06-18 10:48:34.240 5374146 11796536 11829302 8 2008-06-17 13:36:40.310 2010-03-01 22:23:45.487 5374085 11796574 11829336 10 2008-06-17 13:36:40.310 2010-03-30 14:54:29.370 5374085 917590 950356 11 2007-01-30 09:44:32.403 2007-05-24 15:39:53.757 718 917589 950355 10 2007-01-30 09:44:32.403 2007-05-23 12:53:44.780 718 11796573 11829335 62 2007-01-30 09:44:32.403 2010-03-30 14:54:51.237 718 917592 950358 4 2007-05-23 12:01:13.340 2007-05-24 15:42:06.337 917575 11796575 11829337 8 2010-03-01 22:54:03.393 2010-03-01 23:44:47.897 11240205 917591 950357 3 2007-05-23 12:01:13.340 2007-05-23 12:50:01.663 917575 11796578 11829340 27 2008-06-17 15:47:42.157 2010-03-29 17:01:47.840 5374134 11796577 11829339 39 2008-06-17 16:00:47.667 2010-03-30 14:49:13.677 5374151 11796580 11829342 40 2008-06-17 16:00:47.667 2010-03-31 14:22:42.200 5374151 917580 950347 9 2007-01-30 09:44:32.403 2007-05-23 12:50:44.447 718 11796579 11829341 28 2008-06-17 15:47:42.157 2010-03-31 14:22:42.280 5374134 917579 950346 8 2007-01-30 09:44:32.403 2007-05-23 12:43:29.233 718 11796582 11829344 26 2008-08-18 17:36:24.903 2010-03-30 14:49:13.557 6258712 11796581 11829343 48 2008-06-17 15:57:43.497 2010-03-30 14:49:13.353 5374146 11796584 11829346 27 2008-08-18 17:36:24.903 2010-03-31 14:24:01.060 6258712 11796583 11829345 18 2008-06-17 16:59:36.143 2010-03-30 14:49:13.627 5374197 11796586 11829348 33 2008-06-17 15:56:12.620 2010-03-30 14:49:13.447 5374142 11796585 11829347 49 2008-06-17 15:57:43.497 2010-03-31 14:23:28.483 5374146 11796568 11829331 88 2007-10-18 09:59:11.053 2010-03-30 15:14:46.673 2162701 11796570 11829333 89 2007-10-18 09:59:11.053 2010-03-31 14:17:50.360 2162701 13926699 13959461 80 2007-01-30 09:44:32.403 2010-05-12 12:16:35.960 718 11763729 11240565 2010-03-22 13:24:09.867 2010-03-22 13:24:09.867 6384390 1 11403389 11796490 11829258 26 2008-06-17 15:47:42.157 2010-03-29 16:55:15.817 5374134 11796488 11829256 25 2008-06-17 15:47:42.157 2010-03-29 16:47:47.370 5374134 11796486 11829254 24 2008-06-17 15:47:42.157 2010-02-23 11:28:42.643 5374134 13926688 13959450 16 2008-06-17 17:17:28.480 2010-05-12 15:14:48.587 5374220 2195472 2162705 2195469 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. *It is important to format the filenames with a single dot '.' e.g. a filename formatted like T.f00000.ppm isn't supported, but Tf00000.ppm is okay, in this case you would pass the in argument with Tf#.ppm.*| | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-num=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-non-interesting-events \\ | \[yes\] \\ | If saving events, save non interesting events in addition to interesting event. Default is to not save non interesting events. \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \-mbari-mosaic-benthic-stills | \[no\] | Implements good choice of options to experiment with processing still images from a still or moving camera traversing the sea bottom. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --mbari-cache-size=2 --mbari-max-WTA-points=15 --mbari-max-evolve-msec=15000 --vc-type=OIC --use-random=false --test-mode=true --oricomp-type=Steerable --mbari-cache-size=2 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-benthic-video | \[no\] | Implements good choice of options to experiment with processing video from a moving camera traversing the sea bottom. EQUIVALENT TO: --mbari-saliency-dist=5 --mbari-tracking-mode=NearestNeighbor --mbari-saliency-input-image=DiffMean --mbari-segment-algorithm-input-image=MaxRGB --vc-type=O:5IC --use-random=false --test-mode=true --ori-interaction=None --oricomp-type=Steerable --mbari-cache-size=15 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-midwater-video | \[no\] | Implements good choice of options to experiment with processing video from a moving camera traversing the midwater sea column. EQUIVALENT TO: --mbari-saliency-dist=5 --mbari-tracking-mode=KalmanFilter --mbari-saliency-input-image=DiffMean --mbari-segment-algorithm-input-image=MaxRGB --vc-type=O:5IC --use-random=false --test-mode=true --mbari-cache-size=10 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-mosaic-stills {note:title=this option is not supported in pmbarivision} | \[no\] | Implements good choice of options to experiment with still frames collected from a moving camera in mosaic form. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --boring-sm-mv=0.25 --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --vc-type=Variance --use-random=false --mbari-saliency-input-image=Raw --mbari-cache-size=2 --mbari-max-WTA-points=25 --mbari-max-evolve-msec=15000 \\ | | \-mbari-timelapse-stills {note:title=this option is not supported in pmbarivision} | \[no\] | Implements good choice of options to experiment with still frames collected from a stationary time-lapse camera. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=NearestNeighbor --mbari-keep-boring-WTA-points=yes --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --mbari-cache-size=10 --qtime-decay=1.0 --vc-type=Variance --use-random=false --mbari-max-WTA-points=30 --mbari-max-evolve-msec=15000 --use-random=false --use-older-version=false \\ | | \-mbari-timelapse-rover-stills | \[no\] | Implements good choice of options to experiment with time-lapse still frames collected from a benthic moving camera . EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --qtime-decay=1.0 --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --vc-type=O:5IC --use-random=false --mbari-max-WTA-points=15 --mbari-max-evolve-msec=15000 \\ | | \--mbari-max-WTA-points= | \[20\] | Maximum number of winner-take-all points to find in each frame \\ | | \--mbari-max-evolve-msec= | \[500\] | Maximum amount of time in milliseconds to evolve the brain until stopping \\ | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average. \\ | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Tracking mode used to track events between frames \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-segment-algorithm-input-image= | \[MaxRGB\] \\ | Segment algorithm input images type \\ | | \--mbari-segment-algorithm-se-type= | \[benthic\] \\ | Jerome Mariette's segmentation algorithm structure element test \\ | | \--mbari-segment-input-image= | \[DiffMean\] \\ | Saliency input image type \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image. *Important* this only masks the area to look for detections - it does not mask the area from the saliency computation. \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | | \--mbari-min-event-frames= | \[1\] \\ | The minimum number of frames an event must be to be candidate \\ | | \--mbari-max-event-frames= \\ | \[-1\] \\ | The maximum number of frames an event can be, to be candidate. Defaults to infinite \\ | | \--mbari-saliency-dist= \\ | \[5\] \\ | The number of frames to delay between saliency map computations Reduce this to improve your detection rate. Warning reducing this *will* increase your computation time. \\ |]]> 2162702 2195468 2162701 2195467 2162700 11796512 11829279 12 2010-03-22 12:51:54.710 2010-03-30 14:33:03.063 11240565 11796511 11829278 11 2010-03-22 12:51:54.710 2010-03-30 14:32:48.407 11240565 11796514 11829281 13 2010-03-22 12:51:54.710 2010-03-30 14:34:03.577 11240565 11796508 11829275 35 2008-06-17 16:00:47.667 2010-03-01 22:23:29.010 5374151 11796507 11829274 9 2010-03-22 12:51:54.710 2010-03-30 14:14:29.847 11240565 11796510 11829277 10 2010-03-22 12:51:54.710 2010-03-30 14:16:08.910 11240565 3604626 3 917575 2008-04-25 00:39:15.043 2008-04-25 00:39:15.043 11796520 11829287 19 2010-03-22 12:51:54.710 2010-03-30 14:37:08.113 11240565 11796519 11829286 18 2010-03-22 12:51:54.710 2010-03-30 14:36:34.853 11240565 11796521 11829288 20 2010-03-22 12:51:54.710 2010-03-30 14:37:32.007 11240565 11796516 11829283 15 2010-03-22 12:51:54.710 2010-03-30 14:35:34.947 11240565 11796515 11829282 14 2010-03-22 12:51:54.710 2010-03-30 14:35:22.087 11240565 11796518 11829285 17 2010-03-22 12:51:54.710 2010-03-30 14:36:16.320 11240565 4620298 2 927 2008-05-30 15:44:15.047 2008-05-30 15:44:15.047 11796517 11829284 16 2010-03-22 12:51:54.710 2010-03-30 14:35:51.777 11240565 4620297 1 2162701 2008-05-30 15:43:15.047 2008-05-30 15:43:15.047 2195492 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} {info:title=}Make sure in /opt/condor-xxxxxx/etc/condor_config line reads: DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD {info} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat} h3.     Configuring Condor Change the following value in the /opt/condor-xxxxxxx/local.xxxxxx/condor_config.local \\ {noformat} ## When is this machine willing to start a job? START = TRUE ## When to suspend a job? SUSPEND = FALSE ## When to nicely stop a job? ## (as opposed to killing it instantaneously) PREEMPT = FALSE ## When to instantaneously kill a preempting job ## (e.g. if a job is in the pre-empting stage for too long) KILL = FALSE {noformat}\\ \\ \\ \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.     Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat} h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ \\ h3.     Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ The web service provided condains the service (src/org/mbari/aved/webservice/server/AvedService.java) and an exemple to request it (src/org/mbari/aved/webservice/client/AvedClient.java). Before deploying the web-service, you have to edit the java code in order to provide the user Condor is gonna run with and the computer sets. For that edit the file AvedService.java in src/org/mbari/aved/webservice/server {noformat} public static String SCHEDD_LOCATION = "http://host.domain.name.org:8181"; public static String USER = "aved"; {noformat} Then, compile the source by tapping {noformat} ant {noformat} If everything is going well, you should see a BUILD SUCCESSFULL printed, and a build folder should have been created. In these folder you'll find a AvedService.aar file what is the web-service \! To deploy it, just copy and past this file into your application server directory, and the jars from the jars into the application server lib directory: {noformat} cp build/AvedService.aar /webapps/axis2/WEB-INF/services/ cp jars/*.jar /webapps/axis2/WEB-INF/lib/ {noformat} Restart tomcat, and check with your browser if your web-service is up by tapping [http://host:8080/axis2/services/listServices], AvedService should be listed. The AVED web-service requires 4 envirenmental variables: {noformat} export MBARIVISIONROOT= export JAVA_HOME= export CONDOR_CONFIG=/opt/condor-xxxxxxxxx/etc/condor_config export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} You can know test it with the client code provided \! \\ The web service is composed of 3 functions:             - OMElement sendJobToAved (String path): this function takes for parameter the path of the video to be processed and return an XML file with node1=the cluster number and node2=the job number             - OMElement getJobStatus (int cluster, int job): this function takes the cluster number and the job number and return the job status (1: Idle, 2:Running, 3:Removed, 4:Completed, 5:Held).             - OMElement getResult (int cluster, int job): this function takes the cluster number and the job number and return the XML result of the processing. The web service client is basicly a java code what send a job to AVED wait until the status id is at 4 (completed) and get the result. \\ \\ h3.     Installing the AVED web-service as a service on Linux * Create tomcat.sh file in /etc/profile.d then add the following to it: {noformat} export JAVA_HOME= export MBARIVISIONROOT= export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} * Create tomcat file in /etc/init.d then add the following to it: {noformat} . /etc/profile.d/tomcat.sh /bin/catalina.sh start {noformat} \* Add soft links to the tomcat startup script {noformat} ln -s /etc/init.d/tomcat /etc/rc2.d/S100tomcat ln -s /etc/init.d/tomcat /etc/rc2.d/K100tomcat {noformat} Start the tomcat service \\ {noformat} service tomcat start {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 2162725 11796493 11829260 45 2008-06-17 15:57:43.497 2010-03-01 22:20:57.487 5374146 11796494 11829261 46 2008-06-17 15:57:43.497 2010-03-30 13:11:49.787 5374146 11796503 11829270 7 2010-03-22 12:51:54.710 2010-03-30 14:10:24.027 11240565 11796505 11829272 8 2010-03-22 12:51:54.710 2010-03-30 14:10:53.167 11240565 11796500 11829267 4 2010-03-22 12:51:54.710 2010-03-22 13:25:15.980 11240565 11796501 11829268 5 2010-03-22 12:51:54.710 2010-03-30 14:08:54.243 11240565 11796502 11829269 6 2010-03-22 12:51:54.710 2010-03-30 14:09:39.233 11240565 6259065 6226283 14 2008-08-18 17:36:24.903 2008-09-04 14:36:39.810 6258712 6259063 6226281 9 2008-06-17 15:56:12.620 2008-08-18 18:51:20.687 5374142 6259060 6226278 13 2008-08-18 17:36:24.903 2008-09-04 14:33:00.080 6258712 6259059 6226277 12 2008-08-18 17:36:24.903 2008-08-18 19:24:52.980 6258712 6259074 6226292 11 2008-06-17 15:57:43.497 2008-08-22 15:41:58.447 5374146 6259072 6226290 10 2008-06-17 15:56:12.620 2008-09-04 14:45:36.457 5374142 6259070 6226288 16 2008-08-18 17:36:24.903 2008-09-04 15:00:19.037 6258712 6259067 6226285 15 2008-08-18 17:36:24.903 2008-09-04 14:57:43.817 6258712 6259068 6226286 72 2007-10-18 09:59:11.053 2008-08-18 19:03:09.317 2162701 6259080 6226298 13 2008-06-17 15:57:43.497 2008-09-04 16:42:42.917 5374146 6259077 6226295 12 2008-06-17 15:57:43.497 2008-09-04 16:18:06.967 5374146 6259078 6226296 20 2008-06-17 16:00:47.667 2008-09-04 16:40:51.830 5374151 6259076 6226294 19 2008-06-17 16:00:47.667 2008-08-18 17:32:31.540 5374151 6259087 6226305 21 2008-06-17 16:00:47.667 2008-09-04 16:43:39.997 5374151 6259089 6226307 22 2008-06-17 16:00:47.667 2008-09-05 14:00:06.973 5374151 1179656 1212424 12 2007-01-30 09:44:32.403 2007-05-24 15:40:42.537 718 9797766 9830535 9 2008-06-17 16:59:36.143 2009-03-19 09:58:08.600 5374197 9797767 9830536 10 2008-06-17 16:59:36.143 2009-04-21 21:23:17.487 5374197 15204367 15237135 81 2007-01-30 09:44:32.403 2010-08-03 15:25:06.653 718 1179812 1212579 4 2007-02-21 13:30:57.423 2007-02-21 16:33:30.477 927 1179813 1212580 5 2007-02-21 13:30:57.423 2007-07-09 10:08:18.877 927 14614783 2162701 2010-08-30 15:15:40.137 2010-08-30 15:15:40.137 14614782 2162701 2010-08-30 15:15:40.137 2010-08-30 15:15:40.137 14614781 2162701 2010-08-30 15:15:40.137 2010-08-30 15:15:40.137 14614780 2162701 2010-08-30 15:15:40.137 2010-08-30 15:15:40.137 14614785 2162701 2010-08-30 15:15:40.137 2010-08-30 15:15:40.137 14614784 2162701 2010-08-30 15:15:40.137 2010-08-30 15:15:40.137 14614779 2162701 2010-08-30 15:15:40.137 2010-08-30 15:15:40.137 14614778 2162701 2010-08-30 15:15:40.137 2010-08-30 15:15:40.137 6225941 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is diminishing, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat} When you are done, you can skip to [step 6|mbarivision Installation - Step 6. Build and Install mbarivision or pmbarivision], or continue to the next optional step [AVED Installation - Step 5. Build and install Berkeley MPEG Encoder|mbarivision Installation - Step 5. Build and install Berkeley MPEG Encoder (optional)]\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 6258712 1179758 1212525 5 2007-05-23 12:01:13.340 2007-05-24 15:42:38.857 917575 11829744 11796990 9371804 9404554 19 2008-08-18 17:36:24.903 2009-02-20 16:38:44.537 6258712 6258993 6226214 10 2008-06-17 15:57:43.497 2008-07-03 12:46:56.017 5374146 11829752 11796998 9371800 9404552 16 2008-06-17 15:57:43.497 2009-02-20 17:25:38.510 5374146 9371802 9404553 13 2008-06-17 15:56:12.620 2009-02-20 16:38:16.770 5374142 9371798 9404551 15 2008-06-17 15:57:43.497 2009-02-20 16:32:06.470 5374146 9371792 9404547 7 2008-06-17 16:59:36.143 2008-08-18 17:33:15.490 5374197 9371788 9404543 17 2008-08-18 17:36:24.903 2008-09-04 15:05:30.687 6258712 9371789 9404544 12 2008-06-17 15:56:12.620 2009-02-20 16:34:22.717 5374142 9371790 9404545 18 2008-08-18 17:36:24.903 2009-02-20 16:37:23.553 6258712 9371786 9404541 11 2008-06-17 15:56:12.620 2008-09-04 15:46:27.633 5374142 35 927 2007-02-21 13:48:13.860 2007-02-21 13:48:13.860 4570 1 9371784 9404539 14 2008-06-17 15:57:43.497 2008-09-04 16:44:40.280 5374146 9371782 9404537 6 2008-06-17 15:47:42.157 2008-06-17 17:28:19.897 5374134 41 927 2007-02-21 16:40:22.200 2007-02-21 16:40:22.200 798 1 10355113 10387850 12 2008-06-17 15:47:42.157 2009-06-24 13:53:42.987 5374134 10355111 10387848 11 2008-06-17 15:47:42.157 2009-06-24 13:13:52.507 5374134 10355102 10387839 8 2008-06-17 15:47:42.157 2009-03-20 12:43:52.850 5374134 10355106 10387843 18 2008-06-17 15:57:43.497 2009-03-19 09:53:40.057 5374146 10355105 10387842 10 2008-06-17 15:47:42.157 2009-06-24 13:12:12.683 5374134 10355104 10387841 9 2008-06-17 15:47:42.157 2009-06-24 13:08:15.157 5374134 11829299 ./install {noformat}]]> 11796533 11863638 5374297 2010-04-22 23:43:13.423 2010-04-22 23:43:13.423 11863639 5374297 2010-04-22 23:43:13.423 2010-04-22 23:43:13.423 11863636 5374297 2010-04-22 23:43:13.423 2010-04-22 23:43:13.423 11863637 5374297 2010-04-22 23:43:13.423 2010-04-22 23:43:13.423 11272945 11240205 11272938 /dev/null 2>&1 #on the first of every month, remove files older than 90 days 00 00 01 * * /usr/local/bin/cleanscratchfiles #at midnight daily rebuild scratch in case new users added or permissions changed 59 23 * * * /usr/local/bin/buildscratch #check disk space every hour and send root alert if getting too full 0 * * * * /usr/local/bin/diskalert {noformat} diskalert {noformat} #!/bin/sh # set -x # Shell script to monitor or watch the disk space # It will send an email to $ADMIN, if the (free available) percentage of space is >= 90%. # ------------------------------------------------------------------------- # Set admin email so that you can get email. ADMIN="root" # set alert level 90% is default ALERT=90 # Exclude list of unwanted monitoring, if several partions then use "|" to separate the partitions. # An example: EXCLUDE_LIST="/dev/hdd1|/dev/hdc5" EXCLUDE_LIST="tempest:/users|tempest:/tempbox:tornado:/Engineering|tornado:/vol/vol1/ProjectLibrary|nanomia.private.net:/nanomiaRAID" # #:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: # function main_prog() { while read output; do #echo $output usep=$(echo $output | awk '{ print $1}' | cut -d'%' -f1) partition=$(echo $output | awk '{print $2}') if [ $usep -ge $ALERT ] ; then echo "Running out of space \"$partition ($usep%)\" on server $(hostname), $(date)" | mail -s "ALERT: Almost out of disk space $usep% on $(hostname)" $ADMIN fi done } if [ "$EXCLUDE_LIST" != "" ] ; then df -lH | grep -vE "^Filesystem|tmpfs|cdrom|${EXCLUDE_LIST}" | awk '{print $5 " " $6}' | main_prog else df -lH | grep -vE "^Filesystem|tmpfs|cdrom" | awk '{print $5 " " $6}' | main_prog fi {noformat} buildscratch {noformat} ! /bin/bash #set -x USERID=`id -u` if [ $USERID != 0 ]; then echo "You must be root to rue buildscratch" exit 0 fi function dowork() { echo "Building $1" #remove all directories and recreate using file containing users users=$(cat /etc/passwd |grep 20| cut -f1 -d ":") pushd /mnt/scratch #change permissions to include all users chmod a+rwx /mnt/scratch #change owner for new directories for dir in $users do if [ ! -d $dir ]; then echo "mkdir $dir" mkdir $dir fi echo "chown $dir:users $dir" chown $dir:users $dir echo "chmod 0777 $dir " chmod 777 $dir done chown aved:aved aved popd #refresh scratch space NFS mounts on all nodes #cexec '/bin/umount /mnt/scratch;/bin/mount /mnt/scratch' } for s in "/mnt/scratch" "/mnt/scratch2" do dowork $s done #rebuild video directories for capture echo "Rebuilding video capture directories" if [ ! -d /mnt/scratch/video ]; then mkdir -p /mnt/scratch/video/capture fi chmod -Rf a+rwx /mnt/scratch/video #rebuild directories for condor if [ ! -d /mnt/scratch/condor ]; then mkdir -p /mnt/scratch/condor -m=0755 fi chown daemon:root /mnt/scratch/condor {noformat} h2. RAID format Install xfsprogs {noformat} yum install xfsprogs {noformat} Reformat NSTOR RAID {noformat} fdisk /dev/sda pvcreate /dev/sda vgdisplay lvcreate -i2 -I4 -l 2198.7G -namedev AVEDRAID {noformat} Reformat RAID filesystem to XFS {noformat} mkfs.xfs -f - L "AVEDRAID" /dev/sda {noformat}]]> 11240197 11240612 11273337 60 2007-01-30 09:44:32.403 2010-03-23 10:43:21.017 718 1179988 1212752 6 2007-05-23 12:01:13.340 2007-06-25 09:48:45.907 917575 8061026 8093788 13 2007-05-23 12:01:13.340 2008-12-17 10:09:59.953 917575 8061024 8093786 12 2007-05-23 12:01:13.340 2008-06-18 13:35:41.427 917575 11240581 11273307 59 2007-01-30 09:44:32.403 2010-03-23 10:43:01.727 718 11240579 11273305 57 2007-01-30 09:44:32.403 2010-03-22 13:01:42.070 718 11240580 11273306 58 2007-01-30 09:44:32.403 2010-03-23 10:42:40.360 718 11403388 718 2010-03-22 12:47:36.880 2010-03-22 12:47:36.880 19733 1 11403389 11240565 2010-03-22 13:24:09.867 2010-04-14 10:23:38.967 8840790 2 11403386 718 2010-03-19 17:00:11.850 2010-03-19 17:00:11.850 19647 1 11403387 718 2010-03-22 12:47:29.480 2010-03-22 12:47:29.480 71590 1 717 19 714 2 2007-01-30 09:44:32.397 2010-03-31 14:19:34.873 11796572 28 11403385 718 2010-03-19 17:00:05.390 2010-03-19 17:00:05.390 71116 1 11240571 11273297 2 2010-03-22 12:51:54.710 2010-03-22 13:01:11.127 11240565 11240572 11273298 3 2010-03-22 12:51:54.710 2010-03-22 13:24:31.437 11240565 11240569 11273295 56 2007-01-30 09:44:32.403 2010-03-22 12:56:28.333 718 11240568 11273294 1 2010-03-22 12:51:54.710 2010-03-22 12:51:54.710 11240565 11240567 11273293 55 2007-01-30 09:44:32.403 2010-03-22 12:50:08.737 718 11240563 11273289 54 2007-01-30 09:44:32.403 2010-03-19 17:02:00.230 718 6258695 6225927 3 2008-08-18 12:56:19.917 2008-08-18 13:07:46.130 6258689 6258697 6225929 4 2008-08-18 12:56:19.917 2008-08-18 13:08:01.907 6258689 11240543 11273271 52 2007-01-30 09:44:32.403 2010-03-19 16:54:02.937 718 6258691 6225924 1 2008-08-18 12:56:19.917 2008-08-18 12:56:19.917 6258689 905 902 1 2007-01-30 09:44:32.403 2007-01-30 09:44:32.403 718 6258694 6225926 2 2008-08-18 12:56:19.917 2008-08-18 13:04:20.637 6258689 11240545 11273273 53 2007-01-30 09:44:32.403 2010-03-19 16:57:08.840 718 906 903 2 2007-01-30 09:44:32.403 2007-02-14 14:52:59.137 718 13664374 13697126 102 2007-10-18 09:59:11.053 2010-06-09 15:14:19.073 2162701 13664378 13697130 42 2008-06-17 15:56:12.620 2010-05-12 15:14:48.687 5374142 11240535 11273267 50 2007-01-30 09:44:32.403 2010-03-01 23:35:12.083 718 11240537 11273269 51 2007-01-30 09:44:32.403 2010-03-19 16:46:22.443 718 6258729 6225958 8 2008-08-18 17:36:24.903 2008-08-18 18:24:58.890 6258712 6258728 6225957 71 2007-10-18 09:59:11.053 2008-08-18 17:36:55.440 2162701 6258726 6225955 8 2008-06-17 15:56:12.620 2008-08-18 17:28:13.520 5374142 6258724 6225953 7 2008-08-18 17:36:24.903 2008-08-18 18:23:59.030 6258712 6258723 6225952 6 2008-08-18 17:36:24.903 2008-08-18 18:23:26.663 6258712 6258722 6225951 5 2008-08-18 17:36:24.903 2008-08-18 18:22:38.940 6258712 6258721 6225950 4 2008-08-18 17:36:24.903 2008-08-18 18:16:19.373 6258712 6258719 6225948 3 2008-08-18 17:36:24.903 2008-08-18 17:53:30.380 6258712 930 927 1 2007-02-21 13:30:57.423 2007-02-21 13:30:57.423 927 6258717 6225946 2 2008-08-18 17:36:24.903 2008-08-18 17:49:19.533 6258712 6258715 6225944 1 2008-08-18 17:36:24.903 2008-08-18 17:36:24.903 6258712 6258713 6225942 70 2007-10-18 09:59:11.053 2008-08-18 17:29:14.190 2162701 6258707 6225937 6 2008-06-17 16:59:36.143 2008-06-18 10:52:57.863 5374197 907 904 3 2007-01-30 09:44:32.403 2007-02-14 14:57:32.190 718 6258704 6225936 18 2008-06-17 16:00:47.667 2008-06-23 11:56:12.347 5374151 6258702 6225934 69 2007-10-18 09:59:11.053 2008-06-23 10:53:31.193 2162701 6258699 6225931 5 2008-08-18 12:56:19.917 2008-08-18 13:40:23.817 6258689 6258700 6225932 7 2008-06-17 15:56:12.620 2008-06-17 17:05:12.110 5374142 13140039 13172805 9 2008-06-17 14:20:48.653 2010-04-13 13:20:01.097 5374105 963 960 2 2007-02-21 13:30:57.423 2007-02-21 13:50:05.737 927 964 961 3 2007-02-21 13:30:57.423 2007-02-21 16:30:12.207 927 13140035 13172801 35 2008-06-17 15:47:42.157 2010-06-02 14:42:18.713 5374134 13140037 13172803 36 2008-06-17 15:47:42.157 2010-06-02 14:42:40.133 5374134 13140034 13172800 34 2008-06-17 15:47:42.157 2010-05-03 12:13:25.990 5374134 13140019 13172787 24 2008-06-17 16:59:36.143 2010-05-27 16:51:09.517 5374197 6258731 6225960 9 2008-08-18 17:36:24.903 2008-08-18 19:03:09.360 6258712 13140016 13172784 22 2008-06-17 16:59:36.143 2010-05-27 16:49:16.553 5374197 6258733 6225962 10 2008-08-18 17:36:24.903 2008-08-18 19:12:16.207 6258712 13140018 13172786 23 2008-06-17 16:59:36.143 2010-05-27 16:50:13.540 5374197 6258735 6225964 11 2008-08-18 17:36:24.903 2008-08-18 19:17:01.347 6258712 13140014 13172782 21 2008-06-17 16:59:36.143 2010-04-22 23:41:02.340 5374197 13435026 5374197 2010-06-09 17:57:16.533 2010-06-09 17:57:16.533 13435027 5374197 2010-06-09 17:57:16.533 2010-06-09 17:57:16.533 13435024 5374197 2010-06-09 17:57:16.533 2010-06-09 17:57:16.533 13435025 5374197 2010-06-09 17:57:16.533 2010-06-09 17:57:16.533 13435022 5374146 2010-06-09 17:52:39.620 2010-06-09 17:52:39.620 9928762 927 2009-05-11 13:56:55.043 2009-05-11 13:56:55.043 91730 1 13435023 5374197 2010-06-09 17:57:16.533 2010-06-09 17:57:16.533 13435021 5374146 2010-06-09 17:52:39.620 2010-06-09 17:52:39.620 5406859 5374109 11862260 5374085 2010-03-31 14:20:21.347 2010-03-31 14:20:21.347 13435010 11797304 2010-06-09 14:41:59.283 2010-06-09 14:41:59.283 5406856 5374105 13435009 11797304 2010-06-09 14:41:59.283 2010-06-09 14:41:59.283 13435008 11797304 2010-06-09 14:41:59.283 2010-06-09 14:41:59.283 9372311 9405044 17 2008-06-17 15:57:43.497 2009-02-20 17:26:07.890 5374146 9372312 9405045 8 2008-06-17 16:59:36.143 2009-02-20 16:40:05.357 5374197 5406899 ... ${HOME}/aved ${HOME}/Xerces-2_7_0 ${HOME}/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. ]]> 5374151 13435033 11240205 2010-06-09 23:15:27.660 2010-06-09 23:15:27.660 13435032 11240205 2010-06-09 23:15:27.660 2010-06-09 23:15:27.660 5406895 > /etc/ld.so.conf cpush /etc/ld.so.conf cexec ldconfig -v {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|mbarivision Installation - Step 6. Build and Install mbarivision or pmbarivision], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|mbarivision Installation - Step 3. Build and Install Transcode].]]> 5374146 5406891 5374142 5406883 if you have libraries in a nonstandard directory | |CPPFLAGS| C/C++/Objective C preprocessor flags, e.g. -I if you have headers in a nonstandard directory | |CXX| C++ compiler command| h3. Building ffmpeg from source  If you cannot get ffmpeg in a RPM, to install ffmpeg from sources, get the last version. Checkout ffmpeg, build, and install (this assumes you have sudo permissions to install applications to /usr): {noformat} svn checkout svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg cd ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now, go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|mbarivision Installation - Step 2. Build and Install XML Libraries]]]> 5374134 2162795 2195562 30 2007-10-18 16:43:05.903 2007-10-22 16:13:34.570 2162725 2162796 2195563 31 2007-10-18 16:43:05.903 2007-10-22 16:14:54.100 2162725 2162797 2195564 32 2007-10-18 16:43:05.903 2007-10-22 16:17:12.947 2162725 2162798 2195565 33 2007-10-18 16:43:05.903 2007-10-22 16:18:24.640 2162725 2162799 2195566 34 2007-10-18 16:43:05.903 2007-10-22 16:20:14.157 2162725 5406944 cp make install mpeg_encode /usr/local/bin {noformat} If installing on a Beowulf cluster, install this to a NFS directory shared across nodes {noformat} install mpeg_encode /home/shared/aved/bin {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision or Pmbarivision|mbarivision Installation - Step 6. Build and Install mbarivision or pmbarivision]. \\ \\ \\ \\ \\ \\ \\]]> 5374197 2162800 2195567 35 2007-10-18 16:43:05.903 2007-10-22 16:37:37.437 2162725 2162801 2195568 36 2007-10-18 16:43:05.903 2007-10-22 16:50:18.380 2162725 2162802 2195569 37 2007-10-18 16:43:05.903 2007-10-23 09:35:38.333 2162725 2162803 2195570 38 2007-10-18 16:43:05.903 2007-10-23 09:36:20.093 2162725 2162804 2195571 39 2007-10-18 16:43:05.903 2007-10-23 09:46:27.957 2162725 2162805 2195572 40 2007-10-18 16:43:05.903 2007-10-23 10:01:45.313 2162725 2162806 2195573 41 2007-10-18 16:43:05.903 2007-10-23 10:14:40.007 2162725 2162807 2195574 42 2007-10-18 16:43:05.903 2007-10-23 10:27:35.893 2162725 2162808 2195575 43 2007-10-18 16:43:05.903 2007-10-23 10:28:08.413 2162725 2162809 2195576 44 2007-10-18 16:43:05.903 2007-10-23 10:39:45.523 2162725 9372339 9405072 7 2008-06-17 15:47:42.157 2009-02-20 16:28:10.713 5374134 2162810 2195577 45 2007-10-18 16:43:05.903 2007-10-23 14:45:07.357 2162725 2162812 2195579 38 2007-10-18 09:59:11.053 2007-10-23 15:49:13.647 2162701 2162811 2195578 37 2007-10-18 09:59:11.053 2007-10-22 15:57:54.983 2162701 2162814 2195581 46 2007-10-18 16:43:05.903 2007-10-23 15:12:48.707 2162725 2162813 2195580 39 2007-10-18 09:59:11.053 2007-10-23 15:59:45.400 2162701 2162815 2195582 47 2007-10-18 16:43:05.903 2007-10-23 16:13:22.870 2162725 11830048 11797304 2162830 2195596 40 2007-10-18 09:59:11.053 2007-10-23 16:01:36.593 2162701 2162833 2195599 43 2007-10-18 09:59:11.053 2007-10-25 14:44:07.337 2162701 2162831 2195597 41 2007-10-18 09:59:11.053 2007-10-25 12:13:12.660 2162701 2162832 2195598 42 2007-10-18 09:59:11.053 2007-10-25 13:48:51.543 2162701 5406964 5374220 2162841 2195607 44 2007-10-18 09:59:11.053 2007-10-25 14:52:05.507 2162701 2162846 2195612 14 2007-01-30 09:44:32.403 2007-11-01 13:19:43.287 718 2162845 2195611 13 2007-01-30 09:44:32.403 2007-06-04 13:15:35.567 718 2162847 2195613 15 2007-01-30 09:44:32.403 2007-11-01 13:20:15.877 718 21364784 21397551 82 2007-01-30 09:44:32.403 2010-10-12 11:06:58.437 718 21364783 21397550 3 2010-03-01 22:44:57.320 2010-03-01 23:32:17.347 11240197 2162744 2195511 15 2007-10-18 09:59:11.053 2007-10-19 11:39:51.297 2162701 14025118 5374220 2010-08-02 13:09:31.373 2010-08-02 13:09:31.373 2162743 2195510 14 2007-10-18 09:59:11.053 2007-10-18 16:38:53.307 2162701 2162746 2195513 17 2007-10-18 09:59:11.053 2007-10-19 11:41:08.297 2162701 2162745 2195512 16 2007-10-18 09:59:11.053 2007-10-19 11:40:29.570 2162701 14025117 5374220 2010-08-02 13:09:31.373 2010-08-02 13:09:31.373 2162740 2195507 16 2007-10-18 09:59:49.230 2007-10-19 10:52:04.040 2162702 2162739 2195506 15 2007-10-18 09:59:49.230 2007-10-19 10:51:24.673 2162702 2162742 2195509 18 2007-10-18 09:59:49.230 2007-10-19 11:24:23.743 2162702 2162741 2195508 17 2007-10-18 09:59:49.230 2007-10-19 11:09:28.237 2162702 2162736 2195503 12 2007-10-18 09:59:49.230 2007-10-19 10:25:39.743 2162702 2162735 2195502 11 2007-10-18 09:59:49.230 2007-10-19 10:18:08.863 2162702 2162738 2195505 14 2007-10-18 09:59:49.230 2007-10-19 10:29:45.583 2162702 2162737 2195504 13 2007-10-18 09:59:49.230 2007-10-19 10:29:21.117 2162702 2162732 2195499 8 2007-10-18 09:59:49.230 2007-10-19 09:50:01.980 2162702 2162731 2195498 7 2007-10-18 09:59:49.230 2007-10-19 09:46:36.733 2162702 2162734 2195501 10 2007-10-18 09:59:49.230 2007-10-19 10:09:07.577 2162702 2162733 2195500 9 2007-10-18 09:59:49.230 2007-10-19 09:55:09.043 2162702 2162759 2195526 10 2007-10-18 16:43:05.903 2007-10-19 14:21:41.367 2162725 2162760 2195527 11 2007-10-18 16:43:05.903 2007-10-19 14:29:58.623 2162725 2162761 2195528 12 2007-10-18 16:43:05.903 2007-10-19 14:30:13.010 2162725 2162762 2195529 13 2007-10-18 16:43:05.903 2007-10-19 14:42:47.657 2162725 2162755 2195522 6 2007-10-18 16:43:05.903 2007-10-19 13:23:59.697 2162725 2162756 2195523 7 2007-10-18 16:43:05.903 2007-10-19 13:43:43.780 2162725 2162757 2195524 8 2007-10-18 16:43:05.903 2007-10-19 14:07:42.207 2162725 2162758 2195525 9 2007-10-18 16:43:05.903 2007-10-19 14:12:36.670 2162725 2162751 2195518 19 2007-10-18 09:59:49.230 2007-10-19 11:25:41.840 2162702 2162752 2195519 4 2007-10-18 16:43:05.903 2007-10-19 13:07:02.047 2162725 2162753 2195520 5 2007-10-18 16:43:05.903 2007-10-19 13:15:18.013 2162725 2162754 2195521 20 2007-10-18 09:59:11.053 2007-10-19 11:47:10.517 2162701 2162747 2195514 18 2007-10-18 09:59:11.053 2007-10-19 11:46:11.423 2162701 2162748 2195515 19 2007-10-18 09:59:11.053 2007-10-19 11:46:53.997 2162701 2162749 2195516 2 2007-10-18 16:43:05.903 2007-10-18 16:45:13.097 2162725 2162750 2195517 3 2007-10-18 16:43:05.903 2007-10-19 11:58:29.250 2162725 2162778 2195545 21 2007-10-18 09:59:11.053 2007-10-19 13:31:51.677 2162701 2162777 2195544 28 2007-10-18 16:43:05.903 2007-10-19 15:27:44.097 2162725 2162776 2195543 27 2007-10-18 16:43:05.903 2007-10-19 15:27:08.443 2162725 2162775 2195542 26 2007-10-18 16:43:05.903 2007-10-19 15:18:26.933 2162725 2162774 2195541 25 2007-10-18 16:43:05.903 2007-10-19 15:13:15.417 2162725 2162773 2195540 24 2007-10-18 16:43:05.903 2007-10-19 15:12:49.433 2162725 2162772 2195539 23 2007-10-18 16:43:05.903 2007-10-19 15:12:04.997 2162725 715 718 2162771 2195538 22 2007-10-18 16:43:05.903 2007-10-19 15:10:38.487 2162725 2162770 2195537 21 2007-10-18 16:43:05.903 2007-10-19 15:10:10.533 2162725 2162769 2195536 20 2007-10-18 16:43:05.903 2007-10-19 15:09:24.017 2162725 2162768 2195535 19 2007-10-18 16:43:05.903 2007-10-19 15:08:48.600 2162725 2162767 2195534 18 2007-10-18 16:43:05.903 2007-10-19 15:08:22.627 2162725 2162766 2195533 17 2007-10-18 16:43:05.903 2007-10-19 15:03:21.297 2162725 11436147 19 2010-02-23 22:29:31.757 2010-02-23 22:29:31.757 2162765 2195532 16 2007-10-18 16:43:05.903 2007-10-19 14:55:10.983 2162725 11436148 19 2010-03-01 15:44:04.870 2010-03-01 15:44:04.870 2162764 2195531 15 2007-10-18 16:43:05.903 2007-10-19 14:50:41.783 2162725 11436145 19 2010-02-23 22:28:53.197 2010-02-23 22:28:53.197 2162763 2195530 14 2007-10-18 16:43:05.903 2007-10-19 14:43:08.133 2162725 11436146 19 2010-02-23 22:29:10.320 2010-02-23 22:29:10.320 2162793 2195560 36 2007-10-18 09:59:11.053 2007-10-22 15:53:55.507 2162701 2162794 2195561 29 2007-10-18 16:43:05.903 2007-10-19 15:28:58.577 2162725 2162791 2195558 34 2007-10-18 09:59:11.053 2007-10-22 14:44:35.750 2162701 2162792 2195559 35 2007-10-18 09:59:11.053 2007-10-22 15:39:09.843 2162701 2162789 2195556 32 2007-10-18 09:59:11.053 2007-10-22 14:17:09.727 2162701 2162790 2195557 33 2007-10-18 09:59:11.053 2007-10-22 14:43:57.140 2162701 2162787 2195554 30 2007-10-18 09:59:11.053 2007-10-22 12:59:54.347 2162701 2162788 2195555 31 2007-10-18 09:59:11.053 2007-10-22 13:15:15.940 2162701 2162785 2195552 28 2007-10-18 09:59:11.053 2007-10-22 10:51:17.587 2162701 2162786 2195553 29 2007-10-18 09:59:11.053 2007-10-22 10:57:12.930 2162701 9372188 9404929 6 2008-06-17 17:17:28.480 2008-06-18 11:32:39.147 5374220 2162783 2195550 26 2007-10-18 09:59:11.053 2007-10-22 10:32:32.697 2162701 2162784 2195551 27 2007-10-18 09:59:11.053 2007-10-22 10:43:20.417 2162701 2162781 2195548 24 2007-10-18 09:59:11.053 2007-10-22 10:22:23.620 2162701 2162782 2195549 25 2007-10-18 09:59:11.053 2007-10-22 10:25:03.770 2162701 2162779 2195546 22 2007-10-18 09:59:11.053 2007-10-19 15:33:34.467 2162701 2162780 2195547 23 2007-10-18 09:59:11.053 2007-10-22 10:21:16.650 2162701 10355553 10388281 34 2007-10-18 09:59:49.230 2009-07-22 17:37:27.197 2162702 10355554 10388282 35 2007-10-18 09:59:49.230 2009-07-23 10:13:55.370 2162702 10355546 10388274 33 2007-10-18 09:59:49.230 2009-05-14 13:53:47.327 2162702 11436150 19 2010-03-01 16:25:10.663 2010-03-01 16:25:10.663 11436149 19 2010-03-01 15:44:04.870 2010-03-01 15:44:04.870 2162710 2195477 2 2007-10-18 09:59:11.053 2007-10-18 14:16:56.767 2162701 2162709 2195476 1 2007-10-18 09:59:11.053 2007-10-18 09:59:11.053 2162701 2162714 2195481 6 2007-10-18 09:59:11.053 2007-10-18 15:24:28.187 2162701 2162713 2195480 5 2007-10-18 09:59:11.053 2007-10-18 15:14:01.303 2162701 2162712 2195479 4 2007-10-18 09:59:11.053 2007-10-18 15:13:40.783 2162701 5406839 5374085 2162711 2195478 3 2007-10-18 09:59:11.053 2007-10-18 14:38:24.187 2162701 5406844 5374092 10355508 10388238 36 2008-06-17 15:57:43.497 2009-07-21 14:46:45.827 5374146 2162726 2195493 1 2007-10-18 16:43:05.903 2007-10-18 16:43:05.903 2162725 2162723 2195490 12 2007-10-18 09:59:11.053 2007-10-18 16:03:54.647 2162701 10355510 10388240 16 2008-06-17 15:56:12.620 2009-07-21 14:51:33.840 5374142 2162724 2195491 13 2007-10-18 09:59:11.053 2007-10-18 16:35:20.417 2162701 10355512 10388242 18 2008-06-17 15:56:12.620 2009-07-21 15:05:46.023 5374142 2162729 2195496 5 2007-10-18 09:59:49.230 2007-10-19 09:45:39.303 2162702 10355511 10388241 17 2008-06-17 15:56:12.620 2009-07-21 15:03:08.477 5374142 2162730 2195497 6 2007-10-18 09:59:49.230 2007-10-19 09:45:59.870 2162702 2162727 2195494 3 2007-10-18 09:59:49.230 2007-10-18 16:09:01.610 2162702 2162728 2195495 4 2007-10-18 09:59:49.230 2007-10-19 09:45:09.397 2162702 2162717 2195484 9 2007-10-18 09:59:11.053 2007-10-18 15:47:25.040 2162701 10355500 10388231 35 2008-06-17 15:57:43.497 2009-07-08 15:40:18.977 5374146 2162718 2195485 10 2007-10-18 09:59:11.053 2007-10-18 15:57:27.157 2162701 2162715 2195482 7 2007-10-18 09:59:11.053 2007-10-18 15:36:52.427 2162701 10355502 10388233 14 2008-06-17 15:56:12.620 2009-02-20 17:27:13.887 5374142 2162716 2195483 8 2007-10-18 09:59:11.053 2007-10-18 15:39:10.363 2162701 10355503 10388234 74 2007-10-18 09:59:11.053 2009-07-01 09:43:57.517 2162701 2162722 2195489 2 2007-10-18 09:59:49.230 2007-10-18 16:07:29.177 2162702 2162719 2195486 11 2007-10-18 09:59:11.053 2007-10-18 15:58:33.997 2162701 10355506 10388236 15 2008-06-17 15:56:12.620 2009-07-21 14:50:32.010 5374142 10355505 10388235 20 2008-08-18 17:36:24.903 2009-02-20 17:28:09.613 6258712 2162720 2195487 1 2007-10-18 09:59:49.230 2007-10-18 09:59:49.230 2162702 9798439 9831190 17 2007-02-21 13:30:57.423 2009-05-12 10:30:24.430 927 9798438 9831189 37 2007-01-30 09:44:32.403 2009-05-12 10:30:24.383 718 9798437 9831188 16 2007-02-21 13:30:57.423 2009-05-11 13:59:07.500 927 9798436 9831187 36 2007-01-30 09:44:32.403 2009-05-11 13:59:07.470 718 13729992 5374142 2010-06-22 17:03:51.867 2010-06-22 17:03:51.867 13729990 5374142 2010-06-22 17:03:51.863 2010-06-22 17:03:51.863 13729991 5374142 2010-06-22 17:03:51.867 2010-06-22 17:03:51.867 13729988 5374142 2010-06-22 17:03:51.863 2010-06-22 17:03:51.863 13729989 5374142 2010-06-22 17:03:51.863 2010-06-22 17:03:51.863 13729987 5374142 2010-06-22 17:03:51.863 2010-06-22 17:03:51.863 13729986 5374142 2010-06-22 17:03:51.863 2010-06-22 17:03:51.863 13729985 5374142 2010-06-22 17:03:51.863 2010-06-22 17:03:51.863 13729984 5374142 2010-06-22 17:03:51.863 2010-06-22 17:03:51.863 9798421 9831172 35 2007-01-30 09:44:32.403 2009-01-13 12:31:01.923 718 13729983 5374142 2010-06-22 17:03:51.863 2010-06-22 17:03:51.863 9798422 9831173 15 2007-02-21 13:30:57.423 2009-05-11 13:58:18.243 927 9798419 9831170 13 2007-02-21 13:30:57.423 2007-11-19 15:03:56.697 927 9798420 9831171 14 2007-02-21 13:30:57.423 2009-05-11 13:56:10.360 927 19300570 19 2012-06-18 17:08:30.137 2012-06-18 17:08:30.137 2031617 927 2007-09-11 16:49:59.170 2007-09-11 17:02:06.993 2957 2 2031620 927 2007-09-11 16:49:59.170 2007-09-11 16:49:59.170 2958 1 2031617 2031621 927 2007-09-11 16:50:09.877 2007-09-11 16:50:09.877 593 1 2031618 2031618 927 2007-09-11 16:50:09.877 2007-09-12 12:10:01.480 963 2 2031619 927 2007-09-11 16:50:20.273 2007-09-11 16:50:20.273 927 1 8356120 8388877 32 2007-01-30 09:44:32.403 2008-07-07 16:18:45.307 718 11862119 5374092 2010-03-30 14:53:43.043 2010-03-30 14:53:43.043 11862118 5374092 2010-03-30 14:53:43.043 2010-03-30 14:53:43.043 11862117 5374092 2010-03-30 14:53:43.043 2010-03-30 14:53:43.043 11862116 5374092 2010-03-30 14:53:43.043 2010-03-30 14:53:43.043 8356126 8388882 34 2007-01-30 09:44:32.403 2009-01-13 12:29:57.980 718 8356123 8388880 33 2007-01-30 09:44:32.403 2009-01-13 12:28:28.353 718 10355224 10387957 25 2008-06-17 15:57:43.497 2009-06-29 13:35:10.543 5374146 10355226 10387959 27 2008-06-17 15:57:43.497 2009-06-29 13:45:19.557 5374146 10355225 10387958 26 2008-06-17 15:57:43.497 2009-06-29 13:38:33.273 5374146 10355220 10387953 22 2008-06-17 15:57:43.497 2009-06-29 13:21:32.767 5374146 10355219 10387952 21 2008-06-17 15:57:43.497 2009-06-29 13:20:37.923 5374146 10355222 10387955 24 2008-06-17 15:57:43.497 2009-06-29 13:25:07.560 5374146 10355221 10387954 23 2008-06-17 15:57:43.497 2009-06-29 13:24:50.777 5374146 10355216 10387949 19 2008-06-17 15:57:43.497 2009-06-24 13:17:00.173 5374146 13205715 5374134 2010-06-02 14:49:17.750 2010-06-02 14:49:17.750 13205714 5374134 2010-06-02 14:49:17.750 2010-06-02 14:49:17.750 10355218 10387951 20 2008-06-17 15:57:43.497 2009-06-29 12:53:59.473 5374146 10355242 10387975 73 2007-10-18 09:59:11.053 2008-09-04 15:01:41.140 2162701 10355236 10387969 23 2008-06-17 16:00:47.667 2008-09-05 14:01:21.050 5374151 10355237 10387970 24 2008-06-17 16:00:47.667 2009-06-30 12:27:58.780 5374151 10355231 10387964 32 2008-06-17 15:57:43.497 2009-06-29 14:52:41.153 5374146 10355233 10387966 33 2008-06-17 15:57:43.497 2009-06-29 14:53:16.807 5374146 10355227 10387960 28 2008-06-17 15:57:43.497 2009-06-29 13:53:46.363 5374146 10355228 10387961 29 2008-06-17 15:57:43.497 2009-06-29 14:08:07.497 5374146 10355229 10387962 30 2008-06-17 15:57:43.497 2009-06-29 14:14:58.910 5374146 10355230 10387963 31 2008-06-17 15:57:43.497 2009-06-29 14:15:17.773 5374146 10355194 10387929 11 2008-06-17 16:59:36.143 2009-04-21 21:30:56.813 5374197 12714565 5374151 2010-05-26 19:01:34.077 2010-05-26 19:01:34.077 12714564 5374151 2010-05-26 19:01:34.077 2010-05-26 19:01:34.077 9798537 9831283 32 2007-10-18 09:59:49.230 2008-10-23 16:41:43.047 2162702 12714567 5374151 2010-05-26 19:01:34.077 2010-05-26 19:01:34.077 12714566 5374151 2010-05-26 19:01:34.077 2010-05-26 19:01:34.077 12714569 5374151 2010-05-26 19:01:34.077 2010-05-26 19:01:34.077 12714568 5374151 2010-05-26 19:01:34.077 2010-05-26 19:01:34.077 12714570 5374151 2010-05-26 19:01:34.077 2010-05-26 19:01:34.077 13205720 5374105 2010-06-02 14:51:47.897 2010-06-02 14:51:47.897 12714560 5374151 2010-05-26 19:01:34.077 2010-05-26 19:01:34.077 13205716 5374134 2010-06-02 14:49:17.750 2010-06-02 14:49:17.750 12714561 5374151 2010-05-26 19:01:34.077 2010-05-26 19:01:34.077 13205717 5374134 2010-06-02 14:49:17.750 2010-06-02 14:49:17.750 12714562 5374151 2010-05-26 19:01:34.077 2010-05-26 19:01:34.077 13205718 5374134 2010-06-02 14:49:17.750 2010-06-02 14:49:17.750 12714563 5374151 2010-05-26 19:01:34.077 2010-05-26 19:01:34.077 13205719 5374134 2010-06-02 14:49:17.750 2010-06-02 14:49:17.750 5407038 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVEDac Installation].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed to use. Passwords for both the root and aved users have been sent to Dhugal. Two additional steps were required for this installation: # Add manual links for the dc1394 control libraries. This was needed to get saliency to compile. {noformat} cd /usr/lib ln -s libdc1394.so.22 libdc1394_control.so ln -s libdc1394.so.22 libdc1394.so {noformat} # Add /usr/local/lib to the /etc/ld.so.conf. This was needed to get the loader to load the dependent libraries (e.g. xercesc) that are by default installed to /usr/local/lib to load. {noformat} echo /usr/local/lib >> /etc/ld.so.conf {noformat}\\ \\ h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVEDac Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a \\ jamstec_runmbarivis_displayalg \\ \\ This will display output, similar to the following. \*NOTE\* Windows display overlapped, not in the cascade pattern shown in this image. Just remember to click and drag them from on top of each other. \\ (click to enlarge)  !ScreenshotAlgorithmRunning.png|thumbnail!\\ \\ OR \\ jamstec_runmbarivis  \\ This will simply spew out the output from mbarivision into the console window.  \\ (click to enlarge)  !ScreenshotJamstecrunmbarivis.png|thumbnail!\\ \\ | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect \\ jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139Z.mov \\ {tip:title=Handy Hint}This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]\\ date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number. \\ E.g. 20080604T063139Z assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} | Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. | cd /home/aved/Video/20080604T063139Z.mov; jamstec_runprocess 20080604T063139Z.mov \\ | h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. *This must be executed in the root directory of the ppm frames*, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. *This must be executed in the root directory of the ppm frames*, Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 5374297 2162939 2195704 12 2007-02-21 13:30:57.423 2007-09-12 12:10:07.863 927 2162940 2195705 16 2007-01-30 09:44:32.403 2007-11-01 13:20:41.967 718 10355299 10388031 34 2008-06-17 15:57:43.497 2009-06-29 14:54:28.970 5374146 10355300 10388032 13 2008-06-17 15:47:42.157 2009-06-24 13:54:34.917 5374134 10355301 10388033 14 2008-06-17 15:47:42.157 2009-07-08 16:46:36.390 5374134 6259357 6226560 5 2008-06-17 14:20:48.653 2008-06-18 11:34:39.877 5374105 924 [AVED XML Schema and Example^SourceMetaData.xsd]                                   \| --------> [AVED XML Schema and Example^EventDetectionParameters.xsd] h2. Data Model {note:title=Important} * AVED indexes output by _Framenumber_ by default. If the input video clip is encoded according to the [UTC|http://en.wikipedia.org/wiki/ISO_8601] format, the timecode will be populated in the _FrameEventSet->timecode_ field. Timecode frequency is calculated based on the _SourceMetaData->frameRate_ field.{note} !AVED Event Classes.jpg! h2. XML Sample {code} {code} ]]> 927 11862259 5374085 2010-03-31 14:20:21.347 2010-03-31 14:20:21.347 12484621 12550157 53 2008-06-17 15:57:43.497 2010-05-12 15:14:48.340 5374146 771 19 2007-01-30 10:34:27.947 2007-01-30 10:34:27.947 772 19 2007-01-30 10:34:27.947 2007-01-30 10:34:27.947 769 19 2007-01-30 10:34:27.947 2007-01-30 10:34:27.947 770 19 2007-01-30 10:34:27.947 2007-01-30 10:34:27.947 767 19 2007-01-30 10:34:27.947 2007-01-30 10:34:27.947 768 19 2007-01-30 10:34:27.947 2007-01-30 10:34:27.947 12320772 11797304 2010-05-11 13:11:34.217 2010-05-11 13:11:34.217 77905 1 765 19 2007-01-30 10:34:27.947 2007-01-30 10:34:27.947 766 19 2007-01-30 10:34:27.947 2007-01-30 10:34:27.947 763 19 2007-01-30 10:34:27.947 2007-01-30 10:34:27.947 12222516 12255284 79 2007-01-30 09:44:32.403 2010-05-06 13:28:27.620 718 764 19 2007-01-30 10:34:27.947 2007-01-30 10:34:27.947 761 19 2007-01-30 10:34:08.023 2007-01-30 10:34:08.023 12222518 12255286 10 2010-05-06 16:10:32.840 2010-05-11 13:19:58.867 11797304 762 19 2007-01-30 10:34:08.027 2007-01-30 10:34:08.027 12222519 12255287 52 2008-06-17 15:57:43.497 2010-04-22 23:41:02.487 5374146 759 19 2007-01-30 10:34:08.023 2007-01-30 10:34:08.023 760 19 2007-01-30 10:34:08.023 2007-01-30 10:34:08.023 12222520 12255288 31 2008-08-18 17:36:24.903 2010-04-22 23:41:02.587 6258712 757 19 2007-01-30 10:34:08.023 2007-01-30 10:34:08.023 12222521 12255289 15 2008-06-17 17:17:28.480 2010-04-29 16:26:52.950 5374220 12222522 12255290 99 2007-10-18 09:59:11.053 2010-05-11 12:43:39.850 2162701 758 19 2007-01-30 10:34:08.023 2007-01-30 10:34:08.023 12222523 12255291 41 2008-06-17 15:56:12.620 2010-05-11 13:18:30.710 5374142 775 19 2007-01-30 10:34:27.950 2007-01-30 10:34:27.950 774 19 2007-01-30 10:34:27.950 2007-01-30 10:34:27.950 773 19 2007-01-30 10:34:27.947 2007-01-30 10:34:27.947 733 19 2007-01-30 09:45:53.420 2007-01-30 09:45:53.420 12222482 12255250 4 2010-05-06 16:10:32.840 2010-05-11 12:43:11.013 11797304 734 19 2007-01-30 09:45:53.420 2007-01-30 09:45:53.420 12222479 12255247 3 2010-05-06 16:10:32.840 2010-05-11 12:42:43.423 11797304 735 19 2007-01-30 09:45:53.420 2007-01-30 09:45:53.420 12222480 12255248 98 2007-10-18 09:59:11.053 2010-05-03 12:18:03.003 2162701 736 19 2007-01-30 09:45:53.420 2007-01-30 09:45:53.420 737 19 2007-01-30 09:45:53.420 2007-01-30 09:45:53.420 12222478 12255246 2 2010-05-06 16:10:32.840 2010-05-10 15:54:28.410 11797304 738 19 2007-01-30 09:45:53.420 2007-01-30 09:45:53.420 739 19 2007-01-30 09:45:53.420 2007-01-30 09:45:53.420 725 19 2007-01-30 09:45:38.170 2007-01-30 09:45:38.170 12222489 12255257 40 2008-06-17 15:56:12.620 2010-05-03 12:22:28.763 5374142 726 19 2007-01-30 09:45:38.170 2007-01-30 09:45:38.170 12222487 12255255 7 2010-05-06 16:10:32.840 2010-05-11 13:13:00.187 11797304 727 19 2007-01-30 09:45:53.417 2007-01-30 09:45:53.417 12222488 12255256 8 2010-05-06 16:10:32.840 2010-05-11 13:15:39.083 11797304 728 19 2007-01-30 09:45:53.417 2007-01-30 09:45:53.417 729 19 2007-01-30 09:45:53.417 2007-01-30 09:45:53.417 12222486 12255254 6 2010-05-06 16:10:32.840 2010-05-11 13:09:43.807 11797304 730 19 2007-01-30 09:45:53.417 2007-01-30 09:45:53.417 731 19 2007-01-30 09:45:53.420 2007-01-30 09:45:53.420 12222484 12255252 5 2010-05-06 16:10:32.840 2010-05-11 13:07:20.557 11797304 732 19 2007-01-30 09:45:53.420 2007-01-30 09:45:53.420 12222498 12255266 41 2007-10-18 09:59:49.230 2010-04-13 13:22:13.850 2162702 750 19 2007-01-30 10:34:08.020 2007-01-30 10:34:08.020 12484706 12550241 64 2010-03-01 22:54:03.393 2010-05-06 10:58:53.197 11240205 12484705 12550240 47 2008-06-17 16:00:47.667 2010-05-25 15:28:00.317 5374151 749 19 2007-01-30 10:34:08.020 2007-01-30 10:34:08.020 752 19 2007-01-30 10:34:08.023 2007-01-30 10:34:08.023 14516268 14549035 103 2007-10-18 09:59:11.053 2010-06-22 16:36:12.723 2162701 12484703 12550238 46 2008-06-17 16:00:47.667 2010-04-22 23:42:06.907 5374151 751 19 2007-01-30 10:34:08.023 2007-01-30 10:34:08.023 754 19 2007-01-30 10:34:08.023 2007-01-30 10:34:08.023 753 19 2007-01-30 10:34:08.023 2007-01-30 10:34:08.023 756 19 2007-01-30 10:34:08.023 2007-01-30 10:34:08.023 755 19 2007-01-30 10:34:08.023 2007-01-30 10:34:08.023 12222491 12255259 9 2010-05-06 16:10:32.840 2010-05-11 13:16:24.463 11797304 12484714 12550249 51 2008-06-17 16:00:47.667 2010-05-25 16:51:43.607 5374151 12484713 12550248 100 2007-10-18 09:59:11.053 2010-05-12 15:14:48.623 2162701 12484712 12550247 50 2008-06-17 16:00:47.667 2010-05-25 16:12:52.917 5374151 12484710 12550245 49 2008-06-17 16:00:47.667 2010-05-25 16:09:42.593 5374151 12484708 12550243 48 2008-06-17 16:00:47.667 2010-05-25 15:58:23.523 5374151 748 19 2007-01-30 10:33:49.330 2007-01-30 10:33:49.330 12222500 12255268 42 2007-10-18 09:59:49.230 2010-05-11 14:45:36.737 2162702 703 19 2007-01-30 09:44:32.403 2007-01-30 09:44:32.403 704 19 2007-01-30 09:44:32.403 2007-01-30 09:44:32.403 701 19 2007-01-30 09:44:32.403 2007-01-30 09:44:32.403 702 19 2007-01-30 09:44:32.403 2007-01-30 09:44:32.403 695 19 2007-01-30 09:44:32.403 2007-01-30 09:44:32.403 696 19 2007-01-30 09:44:32.403 2007-01-30 09:44:32.403 693 19 2007-01-30 09:44:32.403 2007-01-30 09:44:32.403 694 19 2007-01-30 09:44:32.403 2007-01-30 09:44:32.403 699 19 2007-01-30 09:44:32.403 2007-01-30 09:44:32.403 700 19 2007-01-30 09:44:32.403 2007-01-30 09:44:32.403 697 19 2007-01-30 09:44:32.403 2007-01-30 09:44:32.403 698 19 2007-01-30 09:44:32.403 2007-01-30 09:44:32.403 720 19 2007-01-30 09:45:38.170 2007-01-30 09:45:38.170 5505951 2162725 2008-06-18 11:33:22.563 2008-06-18 11:33:22.563 719 19 2007-01-30 09:45:38.170 2007-01-30 09:45:38.170 5505950 2162725 2008-06-18 11:33:22.563 2008-06-18 11:33:22.563 718 19 2007-01-30 09:45:38.170 2007-01-30 09:45:38.170 5505949 2162725 2008-06-18 11:33:22.563 2008-06-18 11:33:22.563 717 19 2007-01-30 09:45:38.170 2007-01-30 09:45:38.170 5505948 2162725 2008-06-18 11:33:22.563 2008-06-18 11:33:22.563 724 19 2007-01-30 09:45:38.170 2007-01-30 09:45:38.170 11797299 11830043 78 2007-01-30 09:44:32.403 2010-04-22 23:43:13.307 718 723 19 2007-01-30 09:45:38.170 2007-01-30 09:45:38.170 722 19 2007-01-30 09:45:38.170 2007-01-30 09:45:38.170 721 19 2007-01-30 09:45:38.170 2007-01-30 09:45:38.170 712 19 2007-01-30 09:45:12.023 2007-01-30 09:45:12.023 12222472 12255240 1 2010-05-06 16:10:32.840 2010-05-06 16:10:32.840 11797304 716 19 2007-01-30 09:45:38.170 2007-01-30 09:45:38.170 5505947 2162725 2008-06-18 11:33:22.563 2008-06-18 11:33:22.563 715 19 2007-01-30 09:45:38.170 2007-01-30 09:45:38.170 5505946 2162725 2008-06-18 11:33:22.563 2008-06-18 11:33:22.563 714 19 2007-01-30 09:45:38.170 2007-01-30 09:45:38.170 5505945 2162725 2008-06-18 11:33:22.563 2008-06-18 11:33:22.563 11797294 11830038 63 2010-03-01 22:54:03.393 2010-05-03 11:58:33.397 11240205 713 19 2007-01-30 09:45:38.170 2007-01-30 09:45:38.170 5374176 5406924 3 2008-06-17 16:00:47.667 2008-06-17 16:47:00.927 5374151 5668953 19 2008-06-23 11:33:09.250 2008-06-23 11:33:09.250 12484757 12550292 68 2008-06-17 16:00:47.667 2010-05-26 18:23:24.153 5374151 5668954 19 2008-06-23 11:33:09.250 2008-06-23 11:33:09.250 12484756 12550291 67 2008-06-17 16:00:47.667 2010-05-26 18:22:25.990 5374151 5668955 19 2008-06-23 11:33:09.250 2008-06-23 11:33:09.250 5668956 19 2008-06-23 11:33:09.250 2008-06-23 11:33:09.250 5668949 19 2008-06-23 11:32:04.670 2008-06-23 11:32:04.670 1835012 1867780 7 2007-05-23 12:01:13.340 2007-08-22 12:20:22.760 917575 12484761 12550296 71 2008-06-17 16:00:47.667 2010-05-26 18:50:34.073 5374151 5374171 5406919 1 2008-06-17 16:00:47.667 2008-06-17 16:00:47.667 5374151 5668950 19 2008-06-23 11:33:09.247 2008-06-23 11:33:09.247 12484760 12550295 70 2008-06-17 16:00:47.667 2010-05-26 18:50:05.130 5374151 5668951 19 2008-06-23 11:33:09.247 2008-06-23 11:33:09.247 12484759 12550294 69 2008-06-17 16:00:47.667 2010-05-26 18:26:23.037 5374151 5374173 5406921 2 2008-06-17 16:00:47.667 2008-06-17 16:46:41.667 5374151 5668952 19 2008-06-23 11:33:09.250 2008-06-23 11:33:09.250 1835013 1867781 8 2007-05-23 12:01:13.340 2007-09-05 13:18:16.503 917575 12484750 12550285 65 2008-06-17 16:00:47.667 2010-05-26 15:22:52.743 5374151 10355963 10388689 25 2008-06-17 15:56:12.620 2009-08-06 16:41:03.693 5374142 10355964 10388690 40 2008-06-17 15:57:43.497 2009-08-13 18:21:00.783 5374146 5374183 5406931 20 2007-10-18 09:59:49.230 2007-10-19 13:10:44.973 2162702 12484748 12550283 64 2008-06-17 16:00:47.667 2010-05-26 15:21:57.267 5374151 5374186 5406934 5 2008-06-17 16:00:47.667 2008-06-17 16:48:47.203 5374151 10355965 10388691 26 2008-06-17 15:56:12.620 2009-08-13 18:23:46.447 5374142 12484747 12550282 63 2008-06-17 16:00:47.667 2010-05-26 15:02:29.383 5374151 12484754 12550289 66 2008-06-17 16:00:47.667 2010-05-26 15:23:45.503 5374151 5668957 19 2008-06-23 11:33:09.250 2008-06-23 11:33:09.250 10355967 10388693 41 2008-06-17 15:57:43.497 2009-08-13 18:28:26.377 5374146 10355969 10388695 14 2008-06-17 16:59:36.143 2009-08-05 16:21:50.410 5374197 5374181 5406928 4 2008-06-17 16:00:47.667 2008-06-17 16:48:08.040 5374151 5374159 5406907 3 2008-06-17 15:57:43.497 2008-06-17 16:22:38.243 5374146 5374161 5406909 4 2008-06-17 15:57:43.497 2008-06-17 16:27:13.193 5374146 5374162 5406910 5 2008-06-17 15:57:43.497 2008-06-17 16:28:53.507 5374146 5374155 5406903 1 2008-06-17 15:57:43.497 2008-06-17 15:57:43.497 5374146 5374157 5406905 2 2008-06-17 15:57:43.497 2008-06-17 16:19:00.617 5374146 10355961 10388687 39 2008-06-17 15:57:43.497 2009-08-05 15:52:29.357 5374146 5374167 5406915 59 2007-10-18 09:59:11.053 2008-06-17 15:59:03.267 2162701 12484766 12550301 74 2008-06-17 16:00:47.667 2010-05-26 18:57:21.647 5374151 12484763 12550298 72 2008-06-17 16:00:47.667 2010-05-26 18:51:07.200 5374151 5374169 5406917 60 2007-10-18 09:59:11.053 2008-06-17 16:32:30.047 2162701 12484764 12550299 73 2008-06-17 16:00:47.667 2010-05-26 18:55:27.433 5374151 5374163 5406911 3 2008-06-17 15:56:12.620 2008-06-17 15:58:25.267 5374142 5374164 5406912 4 2008-06-17 15:56:12.620 2008-06-17 16:30:46.327 5374142 5374165 5406913 5 2008-06-17 15:56:12.620 2008-06-17 16:31:14.590 5374142 12484723 12550258 11 2010-05-06 16:10:32.840 2010-05-12 15:14:48.253 11797304 12484726 12550261 55 2008-06-17 16:00:47.667 2010-05-25 21:02:16.320 5374151 5374144 5406893 57 2007-10-18 09:59:11.053 2008-06-17 15:55:27.897 2162701 12484725 12550260 12 2010-05-06 16:10:32.840 2010-05-25 21:32:24.323 11797304 5374143 5406892 1 2008-06-17 15:56:12.620 2008-06-17 15:56:12.620 5374142 5374140 5406889 56 2007-10-18 09:59:11.053 2008-06-17 15:49:05.877 2162701 12484729 12550264 56 2008-06-17 16:00:47.667 2010-05-25 22:00:17.320 5374151 12484716 12550251 52 2008-06-17 16:00:47.667 2010-05-25 20:55:00.517 5374151 10355997 10388723 28 2008-06-17 15:56:12.620 2009-08-14 17:49:39.303 5374142 5374153 5406901 4 2008-06-17 14:20:48.653 2008-06-17 16:04:35.067 5374105 10355998 10388724 29 2008-06-17 15:56:12.620 2009-08-14 17:52:52.757 5374142 5374152 5406900 3 2008-06-17 14:20:48.653 2008-06-17 14:22:57.163 5374105 1835040 1867808 10 2007-02-21 13:30:57.423 2007-09-11 16:57:27.097 927 12484718 12550253 53 2008-06-17 16:00:47.667 2010-05-25 20:56:04.517 5374151 10355995 10388721 27 2008-06-17 15:56:12.620 2009-08-13 18:29:21.887 5374142 1835039 1867807 9 2007-02-21 13:30:57.423 2007-09-11 16:56:12.787 927 1835038 1867806 8 2007-02-21 13:30:57.423 2007-09-11 16:55:08.143 927 12484720 12550255 54 2008-06-17 16:00:47.667 2010-05-25 20:57:53.113 5374151 1835037 1867805 7 2007-02-21 13:30:57.423 2007-09-11 16:54:12.367 927 5374149 5406898 58 2007-10-18 09:59:11.053 2008-06-17 15:57:04.147 2162701 1835036 1867804 6 2007-02-21 13:30:57.423 2007-07-09 11:21:16.810 927 5374148 5406897 2 2008-06-17 15:56:12.620 2008-06-17 15:56:36.737 5374142 5374147 5406896 3 2008-06-17 15:47:42.157 2008-06-17 15:53:57.327 5374134 5374130 5406880 53 2007-10-18 09:59:11.053 2008-06-17 15:35:44.257 2162701 12484741 12550276 60 2008-06-17 16:00:47.667 2010-05-25 23:35:05.303 5374151 5374128 5406878 52 2007-10-18 09:59:11.053 2008-06-17 15:24:23.340 2162701 12484743 12550278 61 2008-06-17 16:00:47.667 2010-05-26 14:01:25.543 5374151 10355994 10388720 76 2007-10-18 09:59:11.053 2009-08-05 16:32:48.507 2162701 10355993 10388719 22 2008-08-18 17:36:24.903 2009-08-05 15:57:40.870 6258712 5374126 5406876 51 2007-10-18 09:59:11.053 2008-06-17 15:21:38.887 2162701 12484745 12550280 62 2008-06-17 16:00:47.667 2010-05-26 14:04:48.563 5374151 10355992 10388718 42 2008-06-17 15:57:43.497 2009-08-13 18:34:54.117 5374146 5374123 5406873 49 2007-10-18 09:59:11.053 2008-06-17 15:04:59.530 2162701 5374124 5406874 50 2007-10-18 09:59:11.053 2008-06-17 15:20:44.480 2162701 12484731 12550266 57 2008-06-17 16:00:47.667 2010-05-25 23:29:19.793 5374151 5374138 5406887 2 2008-06-17 15:47:42.157 2008-06-17 15:49:16.703 5374134 12484733 12550268 58 2008-06-17 16:00:47.667 2010-05-25 23:33:18.477 5374151 5374135 5406884 55 2007-10-18 09:59:11.053 2008-06-17 15:47:08.237 2162701 5374136 5406885 1 2008-06-17 15:47:42.157 2008-06-17 15:47:42.157 5374134 12484734 12550269 59 2008-06-17 16:00:47.667 2010-05-25 23:34:13.277 5374151 5374132 5406882 54 2007-10-18 09:59:11.053 2008-06-17 15:43:49.220 2162701 5374107 5406858 1 2008-06-17 14:20:48.653 2008-06-17 14:20:48.653 5374105 5374112 5406862 20 2007-01-30 09:44:32.403 2008-06-17 13:00:56.240 718 5374111 5406861 2 2008-06-17 14:20:48.653 2008-06-17 14:21:40.603 5374105 5374113 5406863 45 2007-10-18 09:59:11.053 2007-10-29 14:50:59.423 2162701 5374116 5406866 46 2007-10-18 09:59:11.053 2008-06-17 14:34:18.427 2162701 5374118 5406868 47 2007-10-18 09:59:11.053 2008-06-17 14:43:40.037 2162701 9899832 927 2009-05-12 10:30:36.053 2009-05-12 10:30:36.053 9899833 927 2009-05-12 10:30:36.053 2009-05-12 10:30:36.053 9899834 927 2009-05-12 10:30:36.053 2009-05-12 10:30:36.053 9899835 927 2009-05-12 10:30:36.053 2009-05-12 10:30:36.053 5374121 5406871 48 2007-10-18 09:59:11.053 2008-06-17 14:53:24.337 2162701 10356024 10388750 36 2007-10-18 09:59:49.230 2009-07-23 10:15:10.500 2162702 10356023 10388749 7 2008-06-17 17:17:28.480 2009-03-10 13:16:08.723 5374220 5374094 5406846 1 2008-06-17 13:47:41.367 2008-06-17 13:47:41.367 5374092 5374096 5406848 2 2008-06-17 13:36:40.310 2008-06-17 13:40:54.173 5374085 5374100 5406851 2 2008-06-17 13:47:41.367 2008-06-17 13:54:40.317 5374092 1835052 1867816 11 2007-02-21 13:30:57.423 2007-09-11 16:58:54.423 927 5374103 5406854 3 2008-06-17 13:47:41.367 2008-06-17 14:02:00.877 5374092 10356014 10388740 6 2008-08-18 12:56:19.917 2008-08-18 13:52:33.883 6258689 5374078 5406832 17 2007-01-30 09:44:32.403 2007-11-19 15:04:39.077 718 5374081 5406835 19 2007-01-30 09:44:32.403 2008-06-17 13:00:43.330 718 5374080 5406834 18 2007-01-30 09:44:32.403 2008-06-17 12:51:43.960 718 5374089 5406842 1 2008-06-17 13:36:40.310 2008-06-17 13:36:40.310 5374085 11797003 11829757 2 2010-04-21 11:29:35.767 2010-04-21 11:40:34.000 11796998 11797004 11829758 55 2010-03-01 22:54:03.393 2010-04-21 11:39:22.247 11240205 5374289 5407032 11 2007-05-23 12:01:13.340 2008-06-18 13:34:50.177 917575 11797005 11829759 56 2010-03-01 22:54:03.393 2010-04-21 11:41:57.830 11240205 5374288 5407031 10 2007-05-23 12:01:13.340 2008-06-18 13:33:55.390 917575 10912271 10945026 39 2007-01-30 09:44:32.403 2009-12-15 10:56:29.157 718 11797006 11829760 57 2010-03-01 22:54:03.393 2010-04-21 11:42:15.843 11240205 5374286 5407029 9 2007-05-23 12:01:13.340 2007-09-05 13:27:00.577 917575 11797008 11829762 58 2010-03-01 22:54:03.393 2010-04-21 11:43:35.217 11240205 11797010 11829764 59 2010-03-01 22:54:03.393 2010-04-21 11:44:52.703 11240205 5374283 5407026 26 2007-10-18 09:59:49.230 2008-06-17 17:38:03.800 2162702 5374313 5407053 1 2008-06-18 15:17:24.963 2008-06-18 15:17:24.963 5374297 11797030 11829784 10 2008-06-17 17:17:28.480 2010-04-21 17:19:51.833 5374220 11797032 11829786 36 2008-06-17 15:56:12.620 2010-03-31 14:26:12.143 5374142 11797031 11829785 20 2008-06-17 16:59:36.143 2010-03-31 14:24:47.780 5374197 11797034 11829788 30 2008-08-18 17:36:24.903 2010-03-31 14:26:12.230 6258712 11797033 11829787 51 2008-06-17 15:57:43.497 2010-03-31 14:24:47.843 5374146 11797020 11829774 9 2008-06-17 17:17:28.480 2010-04-13 13:22:01.880 5374220 11797026 11829780 76 2007-01-30 09:44:32.403 2010-04-16 17:14:05.690 718 5374264 5407007 8 2008-06-17 16:00:47.667 2008-06-17 17:13:30.030 5374151 5374263 5407006 7 2008-06-17 15:57:43.497 2008-06-17 17:16:04.817 5374146 5374266 5407009 65 2007-10-18 09:59:11.053 2008-06-18 10:48:34.220 2162701 5374260 5407003 62 2007-10-18 09:59:11.053 2008-06-18 10:47:29.313 2162701 5374259 5407002 61 2007-10-18 09:59:11.053 2008-06-17 16:33:58.427 2162701 5374262 5407005 64 2007-10-18 09:59:11.053 2008-06-18 10:48:02.683 2162701 5374261 5407004 63 2007-10-18 09:59:11.053 2008-06-18 10:47:53.927 2162701 4882442 19 2008-06-03 12:40:37.987 2008-06-03 12:40:37.987 4882441 19 2008-06-03 12:40:37.987 2008-06-03 12:40:37.987 5374255 5406998 29 2007-01-30 09:44:32.403 2008-06-17 17:34:26.350 718 5374257 5407000 5 2008-06-17 13:47:41.367 2008-06-17 17:15:05.720 5374092 4882438 19 2008-06-03 12:40:37.987 2008-06-03 12:40:37.987 5374251 5406994 3 2008-06-17 17:17:28.480 2008-06-17 17:39:18.680 5374220 4882437 19 2008-06-03 12:40:37.987 2008-06-03 12:40:37.987 4882440 19 2008-06-03 12:40:37.987 2008-06-03 12:40:37.987 4882439 19 2008-06-03 12:40:37.987 2008-06-03 12:40:37.987 5374279 5407022 4 2008-06-17 17:17:28.480 2008-06-17 17:43:28.997 5374220 11796996 11829750 53 2010-03-01 22:54:03.393 2010-04-20 11:40:43.553 11240205 5374281 5407024 5 2008-06-17 17:17:28.480 2008-06-18 11:01:12.577 5374220 4882436 19 2008-06-03 12:40:21.547 2008-06-03 12:40:21.547 5374282 5407025 50 2007-10-18 16:43:05.903 2008-06-17 17:13:18.537 2162725 11797002 11829756 1 2010-04-21 11:29:35.767 2010-04-21 11:29:35.767 11796998 5374276 5407019 12 2008-06-17 16:00:47.667 2008-06-18 10:58:18.137 5374151 11797000 11829754 54 2010-03-01 22:54:03.393 2010-04-21 11:25:03.450 11240205 5374278 5407021 30 2007-01-30 09:44:32.403 2008-06-18 10:33:21.747 718 5374271 5407014 9 2008-06-17 16:00:47.667 2008-06-18 10:49:05.747 5374151 11796988 11829742 51 2010-03-01 22:54:03.393 2010-04-15 14:44:43.077 11240205 5374273 5407016 10 2008-06-17 16:00:47.667 2008-06-18 10:54:59.583 5374151 5374274 5407017 11 2008-06-17 16:00:47.667 2008-06-18 10:58:03.140 5374151 5374267 5407010 66 2007-10-18 09:59:11.053 2008-06-18 10:50:13.523 2162701 11796992 11829746 52 2010-03-01 22:54:03.393 2010-04-20 11:12:25.013 11240205 5374269 5407012 5 2008-06-17 16:59:36.143 2008-06-17 17:15:51.033 5374197 5374230 5406973 23 2007-01-30 09:44:32.403 2008-06-17 17:23:43.410 718 5374228 5406971 22 2007-01-30 09:44:32.403 2008-06-17 17:23:32.300 718 5374227 5406970 21 2007-01-30 09:44:32.403 2008-06-17 14:34:18.390 718 5374234 5406977 5 2008-06-17 15:47:42.157 2008-06-17 17:26:34.137 5374134 5374232 5406975 4 2008-06-17 15:47:42.157 2008-06-17 15:58:02.690 5374134 5374231 5406974 24 2007-01-30 09:44:32.403 2008-06-17 17:25:00.953 718 5374223 5406966 5 2008-06-17 13:36:40.310 2008-06-17 17:18:05.483 5374085 5374246 5406989 1 2008-06-17 17:17:28.480 2008-06-17 17:17:28.480 5374220 5374244 5406987 24 2007-10-18 09:59:49.230 2008-06-17 17:13:30.037 2162702 5374249 5406992 2 2008-06-17 17:17:28.480 2008-06-17 17:37:33.577 5374220 5374247 5406990 25 2007-10-18 09:59:49.230 2008-06-17 17:36:45.513 2162702 5374238 5406981 25 2007-01-30 09:44:32.403 2008-06-17 17:25:29.130 718 5374242 5406985 28 2007-01-30 09:44:32.403 2008-06-17 17:33:00.653 718 5374239 5406982 26 2007-01-30 09:44:32.403 2008-06-17 17:31:57.070 718 5374240 5406983 27 2007-01-30 09:44:32.403 2008-06-17 17:32:32.360 718 5374200 5406947 2 2008-06-17 16:59:36.143 2008-06-17 17:03:17.617 5374197 5374199 5406946 1 2008-06-17 16:59:36.143 2008-06-17 16:59:36.143 5374197 11797046 11829799 13 2008-06-17 17:17:28.480 2010-04-22 23:47:40.533 5374220 5374202 5406949 6 2008-06-17 15:56:12.620 2008-06-17 16:31:27.147 5374142 11797044 11829797 12 2008-06-17 17:17:28.480 2010-04-22 23:43:13.433 5374220 5374201 5406948 6 2008-06-17 15:57:43.497 2008-06-17 16:29:04.200 5374146 11797041 11829794 32 2008-06-18 15:17:24.963 2010-03-30 14:54:51.283 5374297 11797042 11829795 11 2008-06-17 17:17:28.480 2010-04-22 23:40:13.203 5374220 5374190 5406937 6 2008-06-17 16:00:47.667 2008-06-17 16:50:14.083 5374151 11797040 11829793 77 2007-01-30 09:44:32.403 2010-04-22 10:17:44.413 718 11797038 11829792 45 2008-06-17 16:00:47.667 2010-04-22 23:41:02.710 5374151 5374191 5406938 21 2007-10-18 09:59:49.230 2008-06-17 16:49:11.787 2162702 11797035 11829789 95 2007-10-18 09:59:11.053 2010-04-15 11:19:28.747 2162701 11797036 11829790 44 2008-06-17 16:00:47.667 2010-03-31 14:25:52.923 5374151 5374212 5406957 49 2007-10-18 16:43:05.903 2008-06-17 17:07:46.220 2162725 5374213 5406958 7 2008-06-17 16:00:47.667 2008-06-17 16:51:43.063 5374151 5374214 5406959 23 2007-10-18 09:59:49.230 2008-06-17 17:07:23.027 2162702 5374215 5406960 4 2008-06-17 13:36:40.310 2008-06-17 17:10:05.053 5374085 5374217 5406962 4 2008-06-17 13:47:41.367 2008-06-17 14:07:39.333 5374092 5374218 5406963 4 2008-06-17 16:59:36.143 2008-06-17 17:05:29.443 5374197 5374203 5406950 3 2008-06-17 16:59:36.143 2008-06-17 17:04:18.323 5374197 5374205 5406952 22 2007-10-18 09:59:49.230 2008-06-17 16:52:36.633 2162702 5374206 5406953 48 2007-10-18 16:43:05.903 2007-10-23 16:13:52.647 2162725 10485897 5374197 2009-08-05 16:20:02.100 2009-08-05 16:20:02.100 6880 1 5374209 5406955 3 2008-06-17 13:36:40.310 2008-06-17 13:55:22.743 5374085 5374418 5407154 27 2007-10-18 09:59:49.230 2008-06-18 11:33:50.050 2162702 691 19 2007-01-30 09:44:32.403 2007-01-30 09:44:32.403 692 19 2007-01-30 09:44:32.403 2007-01-30 09:44:32.403 5374426 5407162 20 2008-06-18 15:17:24.963 2008-06-24 12:24:35.297 5374297 5374424 5407160 19 2008-06-18 15:17:24.963 2008-06-23 10:49:22.173 5374297 5374422 5407158 29 2007-10-18 09:59:49.230 2008-06-24 12:09:24.520 2162702 5374420 5407156 28 2007-10-18 09:59:49.230 2008-06-24 12:08:33.227 2162702 10355718 10388445 12 2008-06-17 16:59:36.143 2009-06-26 16:47:59.570 5374197 10355715 10388442 19 2008-06-17 15:56:12.620 2009-07-21 15:06:05.933 5374142 10355716 10388443 21 2008-08-18 17:36:24.903 2009-07-21 14:51:33.803 6258712 10355721 10388448 13 2008-06-17 16:59:36.143 2009-08-05 16:03:17.447 5374197 5374430 5407166 23 2008-06-18 15:17:24.963 2008-06-24 12:35:30.887 5374297 5374429 5407165 22 2008-06-18 15:17:24.963 2008-06-24 12:34:29.240 5374297 5374427 5407163 21 2008-06-18 15:17:24.963 2008-06-24 12:33:19.423 5374297 10355710 10388437 15 2008-06-17 15:47:42.157 2009-07-08 16:47:28.037 5374134 10355713 10388440 37 2008-06-17 15:57:43.497 2009-07-21 14:53:57.217 5374146 10355714 10388441 38 2008-06-17 15:57:43.497 2009-08-05 15:42:01.140 5374146 10355711 10388438 16 2008-06-17 15:47:42.157 2009-08-05 15:13:56.973 5374134 5374379 5407118 14 2008-06-18 15:17:24.963 2008-06-19 16:25:49.653 5374297 10355723 10388450 25 2008-06-17 16:00:47.667 2009-06-30 12:35:37.133 5374151 10355725 10388452 26 2008-06-17 16:00:47.667 2009-08-05 16:28:32.670 5374151 10355727 10388454 27 2008-06-17 16:00:47.667 2009-08-05 16:30:09.453 5374151 10355729 10388456 75 2007-10-18 09:59:11.053 2009-07-21 14:51:02.100 2162701 5374400 5407139 17 2008-06-18 15:17:24.963 2008-06-23 10:48:16.303 5374297 10355747 10388473 21 2008-06-17 15:56:12.620 2009-08-06 15:09:12.193 5374142 5374399 5407138 16 2008-06-18 15:17:24.963 2008-06-23 10:47:40.180 5374297 5374401 5407140 18 2008-06-18 15:17:24.963 2008-06-23 10:48:33.867 5374297 10355751 10388477 22 2008-06-17 15:56:12.620 2009-08-06 15:14:59.537 5374142 10355753 10388479 23 2008-06-17 15:56:12.620 2009-08-06 16:39:17.360 5374142 5374397 5407136 15 2008-06-18 15:17:24.963 2008-06-19 16:34:12.540 5374297 10355754 10388480 24 2008-06-17 15:56:12.620 2009-08-06 16:40:24.903 5374142 5374408 5407147 17 2008-06-17 16:00:47.667 2008-06-19 13:47:53.673 5374151 10355743 10388469 28 2008-06-17 16:00:47.667 2009-08-05 16:31:33.640 5374151 5374404 5407143 68 2007-10-18 09:59:11.053 2008-06-19 13:41:10.390 2162701 10355745 10388471 20 2008-06-17 15:56:12.620 2009-08-05 15:56:51.057 5374142 5374349 5407088 5 2008-06-18 15:17:24.963 2008-06-19 14:10:40.230 5374297 6946829 6979597 30 2007-10-18 09:59:49.230 2008-06-24 12:16:30.817 2162702 5374347 5407086 4 2008-06-18 15:17:24.963 2008-06-19 13:36:41.810 5374297 11797196 11829945 38 2008-06-17 15:56:12.620 2010-05-03 12:19:35.673 5374142 11797195 11829944 37 2008-06-17 15:56:12.620 2010-04-22 23:41:02.403 5374142 11797198 11829947 39 2008-06-17 15:56:12.620 2010-05-03 12:20:43.100 5374142 5374351 5407090 6 2008-06-18 15:17:24.963 2008-06-19 14:17:09.627 5374297 6946831 6979599 31 2007-10-18 09:59:49.230 2008-10-23 16:24:46.020 2162702 5374362 5407100 7 2008-06-18 15:17:24.963 2008-06-19 14:24:49.557 5374297 5374366 5407105 9 2008-06-18 15:17:24.963 2008-06-19 15:24:20.603 5374297 5374364 5407103 8 2008-06-18 15:17:24.963 2008-06-19 15:20:39.733 5374297 5374374 5407113 11 2008-06-18 15:17:24.963 2008-06-19 15:37:45.970 5374297 5374372 5407111 10 2008-06-18 15:17:24.963 2008-06-19 15:26:03.743 5374297 5374377 5407116 13 2008-06-18 15:17:24.963 2008-06-19 16:23:50.647 5374297 5374375 5407114 12 2008-06-18 15:17:24.963 2008-06-19 15:45:06.440 5374297 5374315 5407055 2 2008-06-18 15:17:24.963 2008-06-19 11:36:36.523 5374297 11797163 11829912 14 2008-06-17 17:17:28.480 2010-04-22 23:50:05.270 5374220 5374323 5407062 3 2008-06-18 15:17:24.963 2008-06-19 11:45:28.363 5374297 11797177 11829926 30 2008-06-17 15:47:42.157 2010-05-03 11:42:46.853 5374134 11797176 11829925 29 2008-06-17 15:47:42.157 2010-03-31 14:23:28.420 5374134 5374325 5407064 67 2007-10-18 09:59:11.053 2008-06-18 10:51:16.387 2162701 5374326 5407065 13 2008-06-17 16:00:47.667 2008-06-18 11:00:31.707 5374151 5374328 5407067 14 2008-06-17 16:00:47.667 2008-06-19 13:41:10.443 5374151 11797185 11829934 62 2010-03-01 22:54:03.393 2010-05-03 11:53:00.327 11240205 5374331 5407070 15 2008-06-17 16:00:47.667 2008-06-19 13:44:32.387 5374151 11797183 11829932 61 2010-03-01 22:54:03.393 2010-05-03 11:45:57.323 11240205 5374333 5407072 16 2008-06-17 16:00:47.667 2008-06-19 13:45:57.930 5374151 11797179 11829928 60 2010-03-01 22:54:03.393 2010-04-21 11:46:08.787 11240205 11797193 11829942 96 2007-10-18 09:59:11.053 2010-04-22 23:41:02.630 2162701 11797194 11829943 97 2007-10-18 09:59:11.053 2010-05-03 12:17:23.053 2162701 11797191 11829940 33 2008-06-17 15:47:42.157 2010-05-03 12:12:26.437 5374134 11797189 11829938 32 2008-06-17 15:47:42.157 2010-05-03 12:11:21.977 5374134 11797187 11829936 31 2008-06-17 15:47:42.157 2010-05-03 11:43:40.420 5374134 10388033 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to tinker with the saliency toolkit, copy it to a separate directory that you won't use in the AVED mbarivision build \! {warning} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 10355301 10388031 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P=/usr/local gmake sudo gmake install {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} Install the XML::Xerces library {noformat} export XERCES_LIB=/usr/lib export XERCES_INCLUDE=/usr/include perl -MCPAN -e 'install XML::Xerces' {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software (optional)] (this step is only required if you need to convert video clips into a suitable format for processing with AVED).]]> 10355299 10388032 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like --prefix, --enable-quitecompile, etc. but don't remove the options above. If you want to tinker with the saliency toolkit, copy it to a separate directory that you won't use in the AVED mbarivision build ! {warning} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 10355300 10387975 10355242 1212525 1179758 13697130 13664378 8093786 8061024 13697126 13664374 8093788 8061026 950340 917573 950339 917572 950341 917574 950344 917577 1212424 1179656 950343 917576 950346 917579 950345 917578 950347 917580 950355 917589 950356 917590 950357 917591 950358 917592 9831188 [AVED XML^SourceMetaData.xsd]                                   \| --------> [AVED XML^EventDetectionParameters.xsd] h2. Data Model {note:title=Important} * AVED indexes output by _Framenumber_ by default. If the input video clip is encoded according to the [UTC|http://en.wikipedia.org/wiki/ISO_8601] format, the timecode will be populated in the _FrameEventSet->timecode_ field. Timecode frequency is calculated based on the _SourceMetaData->frameRate_ field.{note} !AVED Event Classes.jpg! h2. XML Sample {code} {code}]]> 9798437 9831187 9798436 9831190 [AVED XML format^SourceMetaData.xsd]                                   \| --------> [AVED XML format^EventDetectionParameters.xsd] h2. Data Model {note:title=Important} * AVED indexes output by _Framenumber_ by default. If the input video clip is encoded according to the [UTC|http://en.wikipedia.org/wiki/ISO_8601] format, the timecode will be populated in the _FrameEventSet->timecode_ field. Timecode frequency is calculated based on the _SourceMetaData->frameRate_ field.{note} !AVED Event Classes.jpg! h2. XML Sample {code} {code}]]> 9798439 9831189 9798438 9831171 [^SourceMetaData.xsd]                                   \| --------> [^EventDetectionParameters.xsd] h2. Data Model {note:title=Important} * AVED indexes output by _Framenumber_ by default. If the input video clip is encoded according to the [UTC|http://en.wikipedia.org/wiki/ISO_8601] format, the timecode will be populated in the FrameEventSet. Timecode frequency is calculated based on the XML SourceMetaData->frameRate field.{note} !AVED Event Classes.jpg! h2. XML Sample {code} {code}]]> 9798420 9831172 9798421 9831173 [^SourceMetaData.xsd]                                   \| --------> [^EventDetectionParameters.xsd] h2. Data Model {note:title=Important} * AVED indexes output by _Framenumber_ by default. If the input video clip is encoded according to the [UTC|http://en.wikipedia.org/wiki/ISO_8601] format, the timecode will be populated in the _FrameEventSet->timecode_ field. Timecode frequency is calculated based on the _SourceMetaData->frameRate_ field.{note} !AVED Event Classes.jpg! h2. XML Sample {code} {code}]]> 9798422 1212579 1179812 1212580 1179813 9831283 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-non-interesting-events \\ | \[yes\] \\ | If saving events, save non interesting events in addition to interesting event. Default is to not save non interesting events. \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average. \\ | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | | \--mbari-saliency-dist= \\ | \[5\] \\ | The number of frames to delay between saliency map computations. Reduce this to improve your detection rate. Warning reducing this *will* increase your computation time. \\ |]]> 9798537 10388281 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event=ev1,ev1,...,evN; or: all | \[\] \\ | Save cropped events of specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-non-interesting-events \\ | \[yes\] \\ | If saving events, save non interesting events in addition to interesting event. Default is to not save non interesting events. \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average. \\ | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image. *Important* this only masks the area to look for detections - it does not mask the area from the saliency computation. \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | | \--mbari-saliency-dist= \\ | \[5\] \\ | The number of frames to delay between saliency map computations. Reduce this to improve your detection rate. Warning reducing this *will* increase your computation time. \\ |]]> 10355553 10388282 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-non-interesting-events \\ | \[yes\] \\ | If saving events, save non interesting events in addition to interesting event. Default is to not save non interesting events. \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average. \\ | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image. *Important* this only masks the area to look for detections - it does not mask the area from the saliency computation. \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | | \--mbari-saliency-dist= \\ | \[5\] \\ | The number of frames to delay between saliency map computations. Reduce this to improve your detection rate. Warning reducing this *will* increase your computation time. \\ |]]> 10355554 13959450 13926688 1212752 1179988 10388274 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-non-interesting-events \\ | \[yes\] \\ | If saving events, save non interesting events in addition to interesting event. Default is to not save non interesting events. \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average. \\ | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image. *Important* this only masks the area to look for detections - it does not mask the area from the saliency computation. \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | | \--mbari-saliency-dist= \\ | \[5\] \\ | The number of frames to delay between saliency map computations. Reduce this to improve your detection rate. Warning reducing this *will* increase your computation time. \\ |]]> 10355546 13959461 13926699 2195704 [^SourceMetaData.xsd] and references \--------> [^EventDetectionParameters.xsd]]]> 2162939 2195705 2162940 10388234 10355503 10388233 10355502 10388231 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P=/usr/local gmake sudo gmake install {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} Install the XML::Xerces library {noformat} export XERCES_LIB=/usr/local/ib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software (optional)] (this step is only required if you need to convert video clips into a suitable format for processing with AVED).]]> 10355500 10388238 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P=/usr/local gmake sudo gmake install {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} Install the XML::Xerces library {noformat} export XERCES_LIB=/usr/local/ib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software.]]> 10355508 10388236 10355506 10388235 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is diminishing, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue to the next optional step [AVED Installation - Step 5. Build and install Berkeley MPEG Encoder|AVED:AVED Installation - Step 5. Build and install Berkeley MPEG Encoder (optional)]\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 10355505 10388242 10355512 10388241 10355511 10388240 10355510 2195613 2162847 2195612 2162846 2195611 2162845 2195607 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the transcode software Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required to make AVED working, if you provid AVED direcly frames, you can go to the next step. Transcode can be install from a RPM using the yum command, but it is not the basic depot boxes, it can be found on the livna depot that you can download at: [http://rpm.livna.org/rlowiki/]. Download it and install the rpm. Or you can get the code from [http://www.transcoding.org/cgi-bin/transcode]and install it. \\ {noformat} rpm -ivh livna-release-xxxxx.rpm yum install transcode {noformat} If you need to install it from source (rpm transcode are not available for all distributions), first begin by downloading the source from: [http://www.transcoding.org/cgi-bin/transcode], then uncompress the source (bunzip2 is required, if you don't have it: yum install bunzip2). {noformat} bunzip2 transcode-xxxxxx.tar.bz2 tar xvf transcode-xxxxxxx.tar {noformat} Transcode uses shared libraries, here is the list and the RPM packages that provides them:     || Library || RPM Packages || Fedora command \\ || | mpeg2dec | mpeg2dec and mpeg2dec-devel \\ | yum install mpeg2dec; yum install mpeg2dec-devel \\ | | libXv \\ | libXv-devel | yum install libXv-devel \\ |  Then go in the transcode directory:\\ {noformat} cd transcode-xxxxxxx ./configure --disable-lame --disable-libdvdread make sudo make install {noformat}\\ \\ \\ \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162841 2195599 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the transcode software Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required to make AVED working, if you provid AVED direcly frames, you can go to the next step. Transcode can be install from a RPM using the yum command, but it is not the basic depot boxes, it can be found on the livna depot that you can download at: [http://rpm.livna.org/rlowiki/]. Download it and install the rpm. Or you can get the code from [http://www.transcoding.org/cgi-bin/transcode]and install it. \\ {noformat} rpm -ivh livna-release-xxxxx.rpm yum install transcode {noformat} If you need to install it from source (rpm transcode are not available for all distributions), first begin by downloading the source from: [http://www.transcoding.org/cgi-bin/transcode], then uncompress the source (bunzip2 is required, if you don't have it: yum install bunzip2). {noformat} bunzip2 transcode-xxxxxx.tar.bz2 tar xvf transcode-xxxxxxx.tar {noformat} Transcode uses shared libraries, here is the list and the RPM packages that provides them:     || Library || RPM Packages || Fedora command \\ || | mpeg2dec | mpeg2dec and mpeg2dec-devel \\ | yum install mpeg2dec; yum install mpeg2dec-devel \\ | | libXv\\ | libXv-devel | yum install libXv-devel\\ |  Then go in the transcode directory: {noformat} cd transcode-xxxxxxx ./configure --disable make sudo make install {noformat}\\ \\ \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162833 2195597 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the transcode software Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required to make AVED working, if you provid AVED direcly frames, you can go to the next step. Transcode can be install from a RPM using the yum command, but it is not the basic depot boxes, it can be found on the livna depot that you can download at: [http://rpm.livna.org/rlowiki/]. Download it and install the rpm. Or you can get the code from [http://www.transcoding.org/cgi-bin/transcode]and install it.\\ {noformat} rpm -ivh livna-release-xxxxx.rpm yum install transcode {noformat} If you need to install it from source (rpm transcode are not available for all distributions), first begin by downloading the source from: http://www.transcoding.org/cgi-bin/transcode, then uncompress the source (bunzip2 is required, if you don't have it: yum install bunzip2). {noformat}  bunzip2 transcode-xxxxxx.tar.bz2 tar xvf transcode-xxxxxxx.tar  {noformat}\\ \\ \\ \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162831 2195598 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the transcode software Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required to make AVED working, if you provid AVED direcly frames, you can go to the next step. Transcode can be install from a RPM using the yum command, but it is not the basic depot boxes, it can be found on the livna depot that you can download at: [http://rpm.livna.org/rlowiki/]. Download it and install the rpm. Or you can get the code from [http://www.transcoding.org/cgi-bin/transcode]and install it. \\ {noformat} rpm -ivh livna-release-xxxxx.rpm yum install transcode {noformat} If you need to install it from source (rpm transcode are not available for all distributions), first begin by downloading the source from: [http://www.transcoding.org/cgi-bin/transcode], then uncompress the source (bunzip2 is required, if you don't have it: yum install bunzip2). {noformat} bunzip2 transcode-xxxxxx.tar.bz2 tar xvf transcode-xxxxxxx.tar {noformat} Transcode uses shared libraries, here is the list and the RPM packages that provides them:     || Library || RPM Packages || Fedora command \\ || | mpeg2dec | mpeg2dec and mpeg2dec-devel \\ | yum install mpeg2dec; yum install mpeg2dec-devel \\ |  Then go in the transcode directory: {noformat}  cd transcode-xxxxxxx ./configure --disable make sudo make install {noformat}\\ \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162832 2195596 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the transcode software Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required to make AVED working, if you provid AVED direcly frames, you can go to the next step. Transcode can be install from a RPM using the yum command, but it is not the basic depot boxes, it can be found on the livna depot that you can download at: [http://rpm.livna.org/rlowiki/]. Download it and install the rpm. Or you can get the code from [http://www.transcoding.org/cgi-bin/transcode]and install it. {noformat} rpm -ivh livna-release-xxxxx.rpm yum install transcode  {noformat}\\ \\ \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162830 9831170 [^SourceMetaData.xsd]                                   \| --------> [^EventDetectionParameters.xsd]]]> 9798419 2195541 e.g. dcline@mbari {noformat}    h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-6.8.4 export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} [root@nanomia condor]# cd /opt/condor-6.8.4/etc/examples [root@nanomia condor]# cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} [root@nanomia condor]# service condor start {noformat} h3.     MBARI Mail setup for Condor on Linux Condor sends email on job completion, or failure. All Linux server swith Condor and sendmail installed, can be easily configured to send mail correctly to the MBARI exchange server, with the following: Asssuming sendmail is installed, make sure sendmail-cf RPM is installed, and if not *you must install this first* {noformat} [root@nanomia condor]# rpm -qf sendmail-cf sendmail-cf-8.13.1-2 {noformat} On the /etc/mail/sendmail.mc File, only a few things must be changed from the default sendmail configuration to work with the MBARI email server: * Add following line - this change allows sendmail to redirect to the MBARI mail server {noformat} define(`SMART_HOST',`mail.mbari.org') {noformat} * Comment out the following line in /etc/mail/sendmail.mc. This change allows sendmail to receive mail from the Internet and not just the local loopback address. This is not necessary unless your condor is setup as a master, but a good idea if you ever want to test your condor as a master. {noformat} dnl DAEMON_OPTIONS(''Port=smtp,Addr=127.0.0.1,Name=MTA')dnl {noformat} On the /etc/mail/virtusertable File * If your machine runs jobs as the user "aved", the account will need to be forwarded to a legitimate MBARI user, e.g. dclinembari.org. If you are running as a user other than aved, than skip this {noformat} aved@nanomia.shore.mbari.org: dcline@mbari.org {noformat} * Otherwise, forward your mail to a legitimate MBARI user, e.g. dclinembari.org, by adding the following line: {noformat} dcline@nanomia.shore.mbari.org: dcline@mbari.org {noformat} Then restart sendmail: to reset sendmail with the changes in /etc/mail/sendmail.mc and /etc/mail/virtusertable restart the sendmail service \\ {noformat} [root@nanomia mail]/sbin/service sendmail restart {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. 2. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162774 2195542 {noformat}    h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-6.8.4 export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} [root@nanomia condor]# cd /opt/condor-6.8.4/etc/examples [root@nanomia condor]# cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} [root@nanomia condor]# service condor start {noformat} h3.     MBARI Mail setup for Condor on Linux Condor sends email on job completion, or failure. All Linux server swith Condor and sendmail installed, can be easily configured to send mail correctly to the MBARI exchange server, with the following: Asssuming sendmail is installed, make sure sendmail-cf RPM is installed, and if not *you must install this first* {noformat} [root@nanomia condor]# rpm -qf sendmail-cf sendmail-cf-8.13.1-2 {noformat} On the /etc/mail/sendmail.mc File, only a few things must be changed from the default sendmail configuration to work with the MBARI email server: * Add following line - this change allows sendmail to redirect to the MBARI mail server {noformat} define(`SMART_HOST',`mail.mbari.org') {noformat} * Comment out the following line in /etc/mail/sendmail.mc. This change allows sendmail to receive mail from the Internet and not just the local loopback address. This is not necessary unless your condor is setup as a master, but a good idea if you ever want to test your condor as a master. {noformat} dnl DAEMON_OPTIONS(''Port=smtp,Addr=127.0.0.1,Name=MTA')dnl {noformat} On the /etc/mail/virtusertable File * If your machine runs jobs as the user "aved", the account will need to be forwarded to a legitimate MBARI user, e.g. dclinembari.org. If you are running as a user other than aved, than skip this {noformat} aved@nanomia.shore.mbari.org: dcline@mbari.org {noformat} * Otherwise, forward your mail to a legitimate MBARI user, e.g. dclinembari.org, by adding the following line: {noformat} dcline@nanomia.shore.mbari.org: dcline@mbari.org {noformat} Then restart sendmail: to reset sendmail with the changes in /etc/mail/sendmail.mc and /etc/mail/virtusertable restart the sendmail service \\ {noformat} [root@nanomia mail]/sbin/service sendmail restart {noformat}\\ \\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. 2. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162775 11273305 11240579 2195539 e.g. dcline@mbari {noformat}    h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-6.8.4 export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} [root@nanomia condor]# cd /opt/condor-6.8.4/etc/examples [root@nanomia condor]# cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} [root@nanomia condor]# service condor start {noformat} h3.     MBARI Mail setup for Condor on Linux Condor sends email on job completion, or failure. All Linux server swith Condor and sendmail installed, can be easily configured to send mail correctly to the MBARI exchange server, with the following: Asssuming sendmail is installed, make sure sendmail-cf RPM is installed, and if not *you must install this first* {noformat} [root@nanomia condor]# rpm -qf sendmail-cf sendmail-cf-8.13.1-2 {noformat} On the /etc/mail/sendmail.mc File, only a few things must be changed from the default sendmail configuration to work with the MBARI email server: * Add following line - this change allows sendmail to redirect to the MBARI mail server {noformat} define(`SMART_HOST',`mail.mbari.org') {noformat} * Comment out the following line in /etc/mail/sendmail.mc. This change allows sendmail to receive mail from the Internet and not just the local loopback address. This is not necessary unless your condor is setup as a master, but a good idea if you ever want to test your condor as a master. {noformat} dnl DAEMON_OPTIONS(''Port=smtp,Addr=127.0.0.1,Name=MTA')dnl {noformat} On the /etc/mail/virtusertable File * If your machine runs jobs as the user "aved", the account will need to be forwarded to a legitimate MBARI user, e.g. dclinembari.org. If you are running as a user other than aved, than skip this {noformat} aved@nanomia.shore.mbari.org: dcline@mbari.org {noformat} * Otherwise, forward your mail to a legitimate MBARI user, e.g. dclinembari.org, by adding the following line: {noformat} dcline@nanomia.shore.mbari.org: dcline@mbari.org {noformat} Then restart sendmail: to reset sendmail with the changes in /etc/mail/sendmail.mc and /etc/mail/virtusertable restart the sendmail service \\ {noformat} [root@nanomia mail]/sbin/service sendmail restart {noformat}\\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ \\ \\ \\ \\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162772 11273306 11240580 2195540 e.g. dcline@mbari {noformat}    h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-6.8.4 export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} [root@nanomia condor]# cd /opt/condor-6.8.4/etc/examples [root@nanomia condor]# cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} [root@nanomia condor]# service condor start {noformat} h3.     MBARI Mail setup for Condor on Linux Condor sends email on job completion, or failure. All Linux server swith Condor and sendmail installed, can be easily configured to send mail correctly to the MBARI exchange server, with the following: Asssuming sendmail is installed, make sure sendmail-cf RPM is installed, and if not *you must install this first* {noformat} [root@nanomia condor]# rpm -qf sendmail-cf sendmail-cf-8.13.1-2 {noformat} On the /etc/mail/sendmail.mc File, only a few things must be changed from the default sendmail configuration to work with the MBARI email server: * Add following line - this change allows sendmail to redirect to the MBARI mail server {noformat} define(`SMART_HOST',`mail.mbari.org') {noformat} * Comment out the following line in /etc/mail/sendmail.mc. This change allows sendmail to receive mail from the Internet and not just the local loopback address. This is not necessary unless your condor is setup as a master, but a good idea if you ever want to test your condor as a master. {noformat} dnl DAEMON_OPTIONS(''Port=smtp,Addr=127.0.0.1,Name=MTA')dnl {noformat} On the /etc/mail/virtusertable File * If your machine runs jobs as the user "aved", the account will need to be forwarded to a legitimate MBARI user, e.g. dclinembari.org. If you are running as a user other than aved, than skip this {noformat} aved@nanomia.shore.mbari.org: dcline@mbari.org {noformat} * Otherwise, forward your mail to a legitimate MBARI user, e.g. dclinembari.org, by adding the following line: {noformat} dcline@nanomia.shore.mbari.org: dcline@mbari.org {noformat} Then restart sendmail: to reset sendmail with the changes in /etc/mail/sendmail.mc and /etc/mail/virtusertable restart the sendmail service \\ {noformat} [root@nanomia mail]/sbin/service sendmail restart {noformat}\\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ \\ \\ \\ \\ \\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162773 2195545 cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat} h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162778 2195546 cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat} h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162779 2195543 {noformat}   h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat} h5.             Allowing condor to be requested from http \\ Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: {noformat}  condor_reconfig {noformat}\\ \\ \\ \\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162776 2195544 {noformat}\\ h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: {noformat} condor_reconfig {noformat}\\ \\ \\ \\ \\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162777 2195549 cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat} h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162782 2195550 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 --prefix=/usr/local make core sudo make install {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat} h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162783 2195547 cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat} h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162780 2195548 cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat} h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162781 11273307 11240581 13172803 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now, go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|mbarivision Installation - Step 2. Build and Install XML Libraries]]]> 13140037 2195553 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat} h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162786 2195554 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162787 13172805 13140039 2195551 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 --prefix=/usr/local make core sudo make install {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat} h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162784 2195552 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core sudo make install {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat} h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162785 2195526 /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. Download the binaries distribution from http://www.sun.com/java/ and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat}  export JAVA_HOME= {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ h5.              Installing apache Tomcat \\ {noformat}   {noformat}\\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ \\ \\]]> 2162759 2195525 /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing apache Tomcat  \\ \\ \\ \\ \\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ \\ \\]]> 2162758 2195524 /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. h5.              Installing apache Tomcat  \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 2162757 11273289 11240563 2195523 /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service \\ \\ \\ \\ \\ \\]]> 2162756 2195530 /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf  apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ \\ \\]]> 2162763 2195529 /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from http://tomcat.apache.org/ (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat}   tar xzvf  apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat}  ./bin/catalina.sh start {noformat} Start your favorite browser and tape: http://localhost:8080/, if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from http://ws.apache.org/axis2/ (download the war distribution) and copy it into the /webapps folder {noformat}  cp /axis2.war /webapps {noformat} Then on your browser, tape: http://localhost:8080/axis2. You should find at this URL the axis2 presentation page. \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ \\ \\]]> 2162762 2195528 /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} \\ h5.             Installing apache Tomcat \\ {noformat} {noformat}\\ \\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ \\ \\]]> 2162761 2195527 /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} \\ h5.              Installing apache Tomcat \\ {noformat} {noformat}\\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ \\ \\]]> 2162760 2195534 e.g. dcline@mbari {noformat}    h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-6.8.4 export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} [root@nanomia condor]# cd /opt/condor-6.8.4/etc/examples [root@nanomia condor]# cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} [root@nanomia condor]# service condor start {noformat} h3.     MBARI Mail setup for Condor on Linux Condor sends email on job completion, or failure. All Linux server swith Condor and sendmail installed, can be easily configured to send mail correctly to the MBARI exchange server, with the following: Asssuming sendmail is installed, make sure sendmail-cf RPM is installed, and if not *you must install this first* {noformat} [root@nanomia condor]# rpm -qf sendmail-cf sendmail-cf-8.13.1-2 {noformat} On the /etc/mail/sendmail.mc File, only a few things must be changed from the default sendmail configuration to work with the MBARI email server: * Add following line - this change allows sendmail to redirect to the MBARI mail server {noformat} define(`SMART_HOST',`mail.mbari.org') {noformat} * Comment out the following line in /etc/mail/sendmail.mc. This change allows sendmail to receive mail from the Internet and not just the local loopback address. This is not necessary unless your condor is setup as a master, but a good idea if you ever want to test your condor as a master. {noformat} dnl DAEMON_OPTIONS(''Port=smtp,Addr=127.0.0.1,Name=MTA')dnl {noformat} On the /etc/mail/virtusertable File * If your machine runs jobs as the user "aved", the account will need to be forwarded to a legitimate MBARI user, e.g. dclinembari.org. If you are running as a user other than aved, than skip this {noformat} aved@nanomia.shore.mbari.org: dcline@mbari.org {noformat} * Otherwise, forward your mail to a legitimate MBARI user, e.g. dclinembari.org, by adding the following line: {noformat} dcline@nanomia.shore.mbari.org: dcline@mbari.org {noformat} Then restart sendmail: to reset sendmail with the changes in /etc/mail/sendmail.mc and /etc/mail/virtusertable restart the sendmail service {noformat} [root@nanomia mail]/sbin/service sendmail restart {noformat} h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162767 11273295 11240569 2195533 e.g. dcline@mbari {noformat} h2. Installing Condor as a service on Linux \\ * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-6.8.4 export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} [root@nanomia condor]# cd /opt/condor-6.8.4/etc/examples [root@nanomia condor]# cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} [root@nanomia condor]# service condor start {noformat} h1. MBARI Mail setup for Condor on Linux Condor sends email on job completion, or failure. All Linux server swith Condor and sendmail installed, can be easily configured to send mail correctly to the MBARI exchange server, with the following: Asssuming sendmail is installed, make sure sendmail-cf RPM is installed, and if not *you must install this first* {noformat} [root@nanomia condor]# rpm -qf sendmail-cf sendmail-cf-8.13.1-2 {noformat} h2. The /etc/mail/sendmail.mc File Only a few things must be changed from the default sendmail configuration to work with the MBARI email server: * Add following line - this change allows sendmail to redirect to the MBARI mail server {noformat} define(`SMART_HOST',`mail.mbari.org') {noformat} * Comment out the following line in /etc/mail/sendmail.mc. This change allows sendmail to receive mail from the Internet and not just the local loopback address. This is not necessary unless your condor is setup as a master, but a good idea if you ever want to test your condor as a master. {noformat} dnl DAEMON_OPTIONS(''Port=smtp,Addr=127.0.0.1,Name=MTA')dnl {noformat} h2. The /etc/mail/virtusertable File * If your machine runs jobs as the user "aved", the account will need to be forwarded to a legitimate MBARI user, e.g. dclinembari.org. If you are running as a user other than aved, than skip this {noformat} aved@nanomia.shore.mbari.org: dcline@mbari.org {noformat} * Otherwise, forward your mail to a legitimate MBARI user, e.g. dclinembari.org, by adding the following line: {noformat} dcline@nanomia.shore.mbari.org: dcline@mbari.org {noformat} h2. Restart sendmail To reset sendmail with the changes in /etc/mail/sendmail.mc and /etc/mail/virtusertable restart the sendmail service {noformat} [root@nanomia mail]/sbin/service sendmail restart {noformat} h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162766 11273298 h3. Step 6. Change the hostname, e.g. for node 2 {noformat} hostname node8.private.net {noformat} h3. Step 7. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 8. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat} ]]> 11240572 2195532 /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well.\\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162765 11273297 h3. Step 5. Change the hostname, e.g. for node 2 {noformat} hostname node8.private.net {noformat} h3. Step 6. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 7. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat} ]]> 11240571 2195531 /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: http://ant.apache.org/bindownload.cgi. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. {noformat}  tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ \\ \\]]> 2162764 2195538 e.g. dcline@mbari {noformat}    h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-6.8.4 export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} [root@nanomia condor]# cd /opt/condor-6.8.4/etc/examples [root@nanomia condor]# cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} [root@nanomia condor]# service condor start {noformat} h3.     MBARI Mail setup for Condor on Linux Condor sends email on job completion, or failure. All Linux server swith Condor and sendmail installed, can be easily configured to send mail correctly to the MBARI exchange server, with the following: Asssuming sendmail is installed, make sure sendmail-cf RPM is installed, and if not *you must install this first* {noformat} [root@nanomia condor]# rpm -qf sendmail-cf sendmail-cf-8.13.1-2 {noformat} On the /etc/mail/sendmail.mc File, only a few things must be changed from the default sendmail configuration to work with the MBARI email server: * Add following line - this change allows sendmail to redirect to the MBARI mail server {noformat} define(`SMART_HOST',`mail.mbari.org') {noformat} * Comment out the following line in /etc/mail/sendmail.mc. This change allows sendmail to receive mail from the Internet and not just the local loopback address. This is not necessary unless your condor is setup as a master, but a good idea if you ever want to test your condor as a master. {noformat} dnl DAEMON_OPTIONS(''Port=smtp,Addr=127.0.0.1,Name=MTA')dnl {noformat} On the /etc/mail/virtusertable File * If your machine runs jobs as the user "aved", the account will need to be forwarded to a legitimate MBARI user, e.g. dclinembari.org. If you are running as a user other than aved, than skip this {noformat} aved@nanomia.shore.mbari.org: dcline@mbari.org {noformat} * Otherwise, forward your mail to a legitimate MBARI user, e.g. dclinembari.org, by adding the following line: {noformat} dcline@nanomia.shore.mbari.org: dcline@mbari.org {noformat} Then restart sendmail: to reset sendmail with the changes in /etc/mail/sendmail.mc and /etc/mail/virtusertable restart the sendmail service\\ {noformat} [root@nanomia mail]/sbin/service sendmail restart {noformat}\\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ \\ \\ \\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162771 2195537 e.g. dcline@mbari {noformat}    h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-6.8.4 export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} [root@nanomia condor]# cd /opt/condor-6.8.4/etc/examples [root@nanomia condor]# cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} [root@nanomia condor]# service condor start {noformat} h3.     MBARI Mail setup for Condor on Linux Condor sends email on job completion, or failure. All Linux server swith Condor and sendmail installed, can be easily configured to send mail correctly to the MBARI exchange server, with the following: Asssuming sendmail is installed, make sure sendmail-cf RPM is installed, and if not *you must install this first* {noformat} [root@nanomia condor]# rpm -qf sendmail-cf sendmail-cf-8.13.1-2 {noformat} On the /etc/mail/sendmail.mc File, only a few things must be changed from the default sendmail configuration to work with the MBARI email server: * Add following line - this change allows sendmail to redirect to the MBARI mail server {noformat} define(`SMART_HOST',`mail.mbari.org') {noformat} * Comment out the following line in /etc/mail/sendmail.mc. This change allows sendmail to receive mail from the Internet and not just the local loopback address. This is not necessary unless your condor is setup as a master, but a good idea if you ever want to test your condor as a master. {noformat} dnl DAEMON_OPTIONS(''Port=smtp,Addr=127.0.0.1,Name=MTA')dnl {noformat} On the /etc/mail/virtusertable File * If your machine runs jobs as the user "aved", the account will need to be forwarded to a legitimate MBARI user, e.g. dclinembari.org. If you are running as a user other than aved, than skip this {noformat} aved@nanomia.shore.mbari.org: dcline@mbari.org {noformat} * Otherwise, forward your mail to a legitimate MBARI user, e.g. dclinembari.org, by adding the following line: {noformat} dcline@nanomia.shore.mbari.org: dcline@mbari.org {noformat} Then restart sendmail: to reset sendmail with the changes in /etc/mail/sendmail.mc and /etc/mail/virtusertable restart the sendmail service {noformat} [root@nanomia mail]/sbin/service sendmail restart {noformat}\\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ \\ \\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162770 11273294 mount /mount/usbdisk > cd /mount/usbdisk > install -D -m 6644 e1000.ko /lib/modules/2.6.9-1.667smp/kernel/drivers/net/e1000 > /sbin/depmod # Run kudzu to install net driver and setup the network with a static address > kudzu e.g. for node 2, the settings should look something like: /etc/sysconfig/networking/devices/ifcfg-eth0: DEVICE = eth0 ONBOOT = yes BOOTPROTO = static IPADDR = 192.168.1.2 NETMASK = 255.255.255.0 GATEWAY = 192.168.1.254 HWADDR = # Change the hostname, e.g. for node 2 > hostname node8.private.net # Modify the fstab file to include mounts in the fstab file on the thumbdrive # Replace the sshd_config with the file on the thumbdrive > cp -f /mount/usbdisk/sshd_config /etc/ssh ]]> 11240568 2195536 e.g. dcline@mbari {noformat}    h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-6.8.4 export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} [root@nanomia condor]# cd /opt/condor-6.8.4/etc/examples [root@nanomia condor]# cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} [root@nanomia condor]# service condor start {noformat} h3.     MBARI Mail setup for Condor on Linux Condor sends email on job completion, or failure. All Linux server swith Condor and sendmail installed, can be easily configured to send mail correctly to the MBARI exchange server, with the following: Asssuming sendmail is installed, make sure sendmail-cf RPM is installed, and if not *you must install this first* {noformat} [root@nanomia condor]# rpm -qf sendmail-cf sendmail-cf-8.13.1-2 {noformat} On the /etc/mail/sendmail.mc File, only a few things must be changed from the default sendmail configuration to work with the MBARI email server: * Add following line - this change allows sendmail to redirect to the MBARI mail server {noformat} define(`SMART_HOST',`mail.mbari.org') {noformat} * Comment out the following line in /etc/mail/sendmail.mc. This change allows sendmail to receive mail from the Internet and not just the local loopback address. This is not necessary unless your condor is setup as a master, but a good idea if you ever want to test your condor as a master. {noformat} dnl DAEMON_OPTIONS(''Port=smtp,Addr=127.0.0.1,Name=MTA')dnl {noformat} On the /etc/mail/virtusertable File * If your machine runs jobs as the user "aved", the account will need to be forwarded to a legitimate MBARI user, e.g. dclinembari.org. If you are running as a user other than aved, than skip this {noformat} aved@nanomia.shore.mbari.org: dcline@mbari.org {noformat} * Otherwise, forward your mail to a legitimate MBARI user, e.g. dclinembari.org, by adding the following line: {noformat} dcline@nanomia.shore.mbari.org: dcline@mbari.org {noformat} Then restart sendmail: to reset sendmail with the changes in /etc/mail/sendmail.mc and /etc/mail/virtusertable restart the sendmail service {noformat} [root@nanomia mail]/sbin/service sendmail restart {noformat}\\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ \\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162769 11273293 11240567 2195535 e.g. dcline@mbari {noformat}    h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-6.8.4 export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} [root@nanomia condor]# cd /opt/condor-6.8.4/etc/examples [root@nanomia condor]# cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} [root@nanomia condor]# service condor start {noformat} h3.     MBARI Mail setup for Condor on Linux Condor sends email on job completion, or failure. All Linux server swith Condor and sendmail installed, can be easily configured to send mail correctly to the MBARI exchange server, with the following: Asssuming sendmail is installed, make sure sendmail-cf RPM is installed, and if not *you must install this first* {noformat} [root@nanomia condor]# rpm -qf sendmail-cf sendmail-cf-8.13.1-2 {noformat} On the /etc/mail/sendmail.mc File, only a few things must be changed from the default sendmail configuration to work with the MBARI email server: * Add following line - this change allows sendmail to redirect to the MBARI mail server {noformat} define(`SMART_HOST',`mail.mbari.org') {noformat} * Comment out the following line in /etc/mail/sendmail.mc. This change allows sendmail to receive mail from the Internet and not just the local loopback address. This is not necessary unless your condor is setup as a master, but a good idea if you ever want to test your condor as a master. {noformat} dnl DAEMON_OPTIONS(''Port=smtp,Addr=127.0.0.1,Name=MTA')dnl {noformat} On the /etc/mail/virtusertable File * If your machine runs jobs as the user "aved", the account will need to be forwarded to a legitimate MBARI user, e.g. dclinembari.org. If you are running as a user other than aved, than skip this {noformat} aved@nanomia.shore.mbari.org: dcline@mbari.org {noformat} * Otherwise, forward your mail to a legitimate MBARI user, e.g. dclinembari.org, by adding the following line: {noformat} dcline@nanomia.shore.mbari.org: dcline@mbari.org {noformat} Then restart sendmail: to reset sendmail with the changes in /etc/mail/sendmail.mc and /etc/mail/virtusertable restart the sendmail service {noformat} [root@nanomia mail]/sbin/service sendmail restart {noformat} h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162768 11273337 11240612 2195571 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} {info:title=}Make sure in /opt/condor-xxxxxx/etc/condor_config line reads: DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD {info} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.     Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat} \\ h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ \\ \\ h3.     Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ \\ \\ \\ \\ \\ h3.     Installing the AVED web-service as a service on Linux \\ * Create tomcat.sh file in /etc/profile.d then add the following to it:{noformat} {noformat} \\ \\ * Create tomcat.sh file in /etc/profile.d then add the following to it: {noformat} export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * {noformat} {noformat} * Install tomcat service script to execute tomcat and deploy the AVED web-service on bootup {noformat} . /etc/profile.d/tomcat.sh {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the tomcat startup script {noformat} ln -s /etc/init.d/tomcat /etc/rc2.d/S100tomcat ln -s /etc/init.d/tomcat /etc/rc2.d/K100tomcat {noformat} Start the condor service\\ {noformat} service tomcat start {noformat}\\ \\ \\ \\ \\]]> 2162804 2195572 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} {info:title=}Make sure in /opt/condor-xxxxxx/etc/condor_config line reads: DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD {info} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.     Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat} \\ h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ \\ \\ \\ h3.     Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ \\ \\ \\ \\ \\ h3.     Installing the AVED web-service as a service on Linux * Create tomcat.sh file in /etc/profile.d then add the following to it: {noformat} export JAVA_HOME= export MBARIVISIONROOT= export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} * Create tomcat file in /etc/init.d then add the following to it:{noformat} . /etc/profile.d/tomcat.sh /bin/catalina.sh start {noformat}* Add soft links to the tomcat startup script {noformat} ln -s /etc/init.d/tomcat /etc/rc2.d/S100tomcat ln -s /etc/init.d/tomcat /etc/rc2.d/K100tomcat {noformat} Start the tomcat service \\ {noformat} service tomcat start {noformat}\\ \\ \\ \\ \\ \\]]> 2162805 2195573 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} {info:title=}Make sure in /opt/condor-xxxxxx/etc/condor_config line reads: DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD {info} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.     Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat} h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ h3.     Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ The web service provided condains the service (src/org/mbari/aved/webservice/server/AvedService.java) and an exemple to request it (src/org/mbari/aved/webservice/client/AvedClient.java). Before deploying the web-service, you have to edit the java code in order to provide the user Condor is gonna run with and the computer sets. For that edit the file AvedService.java in src/org/mbari/aved/webservice/server {noformat} public static String SCHEDD_LOCATION = "http://host.domain.name.org:8181"; public static String USER = "aved"; {noformat} Then, compile the source by tapping {noformat}  ant {noformat} If everything is going well, you should see a BUILD SUCCESSFULL printed \! \\ \\ h3.     Installing the AVED web-service as a service on Linux * Create tomcat.sh file in /etc/profile.d then add the following to it: {noformat} export JAVA_HOME= export MBARIVISIONROOT= export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} * Create tomcat file in /etc/init.d then add the following to it: {noformat} . /etc/profile.d/tomcat.sh /bin/catalina.sh start {noformat} \* Add soft links to the tomcat startup script {noformat} ln -s /etc/init.d/tomcat /etc/rc2.d/S100tomcat ln -s /etc/init.d/tomcat /etc/rc2.d/K100tomcat {noformat} Start the tomcat service \\ {noformat} service tomcat start {noformat}\\ \\ \\ \\ \\ \\ \\]]> 2162806 2195574 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} {info:title=}Make sure in /opt/condor-xxxxxx/etc/condor_config line reads: DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD {info} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.     Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat} h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ \\ h3.     Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ The web service provided condains the service (src/org/mbari/aved/webservice/server/AvedService.java) and an exemple to request it (src/org/mbari/aved/webservice/client/AvedClient.java). Before deploying the web-service, you have to edit the java code in order to provide the user Condor is gonna run with and the computer sets. For that edit the file AvedService.java in src/org/mbari/aved/webservice/server {noformat} public static String SCHEDD_LOCATION = "http://host.domain.name.org:8181"; public static String USER = "aved"; {noformat} Then, compile the source by tapping {noformat} ant {noformat} If everything is going well, you should see a BUILD SUCCESSFULL printed, and a build folder should have been created. In these folder you'll find a AvedService.aar file what is the web-service \! To deploy it, just copy and past this file into your application server directory, and the jars from the jars into the application server lib directory: {noformat}  cp build/AvedService.aar /webapps/axis2/WEB-INF/services/  cp jars/*.jar /webapps/axis2/WEB-INF/lib/ {noformat}  restart tomcat, and check with your browser if your web-service is up by tapping http://host:8080/axis2/services/listServices, AvedService should be listed. You can know test it with the client code provided \! \\ \\ \\ \\ \\ \\ \\ \\ h3.     Installing the AVED web-service as a service on Linux * Create tomcat.sh file in /etc/profile.d then add the following to it: {noformat} export JAVA_HOME= export MBARIVISIONROOT= export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} * Create tomcat file in /etc/init.d then add the following to it: {noformat} . /etc/profile.d/tomcat.sh /bin/catalina.sh start {noformat} \* Add soft links to the tomcat startup script {noformat} ln -s /etc/init.d/tomcat /etc/rc2.d/S100tomcat ln -s /etc/init.d/tomcat /etc/rc2.d/K100tomcat {noformat} Start the tomcat service \\ {noformat} service tomcat start {noformat}\\ \\ \\ \\ \\ \\ \\ \\]]> 2162807 2195575 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} {info:title=}Make sure in /opt/condor-xxxxxx/etc/condor_config line reads: DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD {info} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.     Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat} h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ h3.     Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ The web service provided condains the service (src/org/mbari/aved/webservice/server/AvedService.java) and an exemple to request it (src/org/mbari/aved/webservice/client/AvedClient.java). Before deploying the web-service, you have to edit the java code in order to provide the user Condor is gonna run with and the computer sets. For that edit the file AvedService.java in src/org/mbari/aved/webservice/server {noformat} public static String SCHEDD_LOCATION = "http://host.domain.name.org:8181"; public static String USER = "aved"; {noformat} Then, compile the source by tapping {noformat} ant {noformat} If everything is going well, you should see a BUILD SUCCESSFULL printed, and a build folder should have been created. In these folder you'll find a AvedService.aar file what is the web-service \! To deploy it, just copy and past this file into your application server directory, and the jars from the jars into the application server lib directory: {noformat} cp build/AvedService.aar /webapps/axis2/WEB-INF/services/ cp jars/*.jar /webapps/axis2/WEB-INF/lib/ {noformat}  restart tomcat, and check with your browser if your web-service is up by tapping [http://host:8080/axis2/services/listServices], AvedService should be listed. You can know test it with the client code provided \! \\ \\ \\ \\ \\ \\ h3.     Installing the AVED web-service as a service on Linux * Create tomcat.sh file in /etc/profile.d then add the following to it: {noformat} export JAVA_HOME= export MBARIVISIONROOT= export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} * Create tomcat file in /etc/init.d then add the following to it: {noformat} . /etc/profile.d/tomcat.sh /bin/catalina.sh start {noformat} \* Add soft links to the tomcat startup script {noformat} ln -s /etc/init.d/tomcat /etc/rc2.d/S100tomcat ln -s /etc/init.d/tomcat /etc/rc2.d/K100tomcat {noformat} Start the tomcat service \\ {noformat} service tomcat start {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\]]> 2162808 2195576 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} {info:title=}Make sure in /opt/condor-xxxxxx/etc/condor_config line reads: DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD {info} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.     Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat} h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ \\ h3.     Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ The web service provided condains the service (src/org/mbari/aved/webservice/server/AvedService.java) and an exemple to request it (src/org/mbari/aved/webservice/client/AvedClient.java). Before deploying the web-service, you have to edit the java code in order to provide the user Condor is gonna run with and the computer sets. For that edit the file AvedService.java in src/org/mbari/aved/webservice/server {noformat} public static String SCHEDD_LOCATION = "http://host.domain.name.org:8181"; public static String USER = "aved"; {noformat} Then, compile the source by tapping {noformat} ant {noformat} If everything is going well, you should see a BUILD SUCCESSFULL printed, and a build folder should have been created. In these folder you'll find a AvedService.aar file what is the web-service \! To deploy it, just copy and past this file into your application server directory, and the jars from the jars into the application server lib directory: {noformat} cp build/AvedService.aar /webapps/axis2/WEB-INF/services/ cp jars/*.jar /webapps/axis2/WEB-INF/lib/ {noformat} Restart tomcat, and check with your browser if your web-service is up by tapping [http://host:8080/axis2/services/listServices], AvedService should be listed. The AVED web-service requires 4 envirenmental variables: {noformat} export MBARIVISIONROOT=  export JAVA_HOME= export CONDOR_CONFIG=/opt/condor-xxxxxxxxx/etc/condor_config export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} You can know test it with the client code provided \! \\ \\ \\ \\ \\ \\ h3.     Installing the AVED web-service as a service on Linux * Create tomcat.sh file in /etc/profile.d then add the following to it: {noformat} export JAVA_HOME= export MBARIVISIONROOT= export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} * Create tomcat file in /etc/init.d then add the following to it: {noformat} . /etc/profile.d/tomcat.sh /bin/catalina.sh start {noformat} \* Add soft links to the tomcat startup script {noformat} ln -s /etc/init.d/tomcat /etc/rc2.d/S100tomcat ln -s /etc/init.d/tomcat /etc/rc2.d/K100tomcat {noformat} Start the tomcat service \\ {noformat} service tomcat start {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 2162809 2195577 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} {info:title=}Make sure in /opt/condor-xxxxxx/etc/condor_config line reads: DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD {info} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.     Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat} h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ \\ \\ h3.     Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ The web service provided condains the service (src/org/mbari/aved/webservice/server/AvedService.java) and an exemple to request it (src/org/mbari/aved/webservice/client/AvedClient.java). Before deploying the web-service, you have to edit the java code in order to provide the user Condor is gonna run with and the computer sets. For that edit the file AvedService.java in src/org/mbari/aved/webservice/server {noformat} public static String SCHEDD_LOCATION = "http://host.domain.name.org:8181"; public static String USER = "aved"; {noformat} Then, compile the source by tapping {noformat} ant {noformat} If everything is going well, you should see a BUILD SUCCESSFULL printed, and a build folder should have been created. In these folder you'll find a AvedService.aar file what is the web-service \! To deploy it, just copy and past this file into your application server directory, and the jars from the jars into the application server lib directory: {noformat} cp build/AvedService.aar /webapps/axis2/WEB-INF/services/ cp jars/*.jar /webapps/axis2/WEB-INF/lib/ {noformat} Restart tomcat, and check with your browser if your web-service is up by tapping [http://host:8080/axis2/services/listServices], AvedService should be listed. The AVED web-service requires 4 envirenmental variables: {noformat} export MBARIVISIONROOT= export JAVA_HOME= export CONDOR_CONFIG=/opt/condor-xxxxxxxxx/etc/condor_config export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} You can know test it with the client code provided \! \\ The web service is composed of 3 functions:             - OMElement sendJobToAved (String path): this function takes for parameter the path of the video to be processed and return an XML file with node1=the cluster number and node2=the job number             - OMElement getJobStatus (int cluster, int job): this function takes the cluster number and the job number and return the job status (1: Idle, 2:Running, 3:Removed, 4:Completed, 5:Held).             - OMElement getResult (int cluster, int job): this function takes the cluster number and the job number and return the XML result of the processing. The web service client is basicly a java code what send a job to AVED wait until the status id is at 4 (completed) and get the result.\\ \\ h3.     Installing the AVED web-service as a service on Linux * Create tomcat.sh file in /etc/profile.d then add the following to it: {noformat} export JAVA_HOME= export MBARIVISIONROOT= export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} * Create tomcat file in /etc/init.d then add the following to it: {noformat} . /etc/profile.d/tomcat.sh /bin/catalina.sh start {noformat} \* Add soft links to the tomcat startup script {noformat} ln -s /etc/init.d/tomcat /etc/rc2.d/S100tomcat ln -s /etc/init.d/tomcat /etc/rc2.d/K100tomcat {noformat} Start the tomcat service \\ {noformat} service tomcat start {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 2162810 2195578 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162811 2195579 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server.\\ h3.  Get and built the transcode software Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required to make AVED working, if you provid AVED direcly frames, you can go to the next step. Get the code from http://www.transcoding.org/cgi-bin/transcode. The sources are provided in a tar.bz2 compression format. Uncompress it where you want to install it: h5.     Preparation for install the transcode software It uses several shared libraries, here is the list and the RPM packages that provides them. || Library || RPM Packages || Fedora command \\ || | libX11 | xorg-x11-proto-devel \\ | yum \-y install xorg-x11-proto-devel | | gcc \\ | gcc-c+\+ | yum \-y install gcc-c+\+ \\ | | tclsh \\ | tclx \\ | yum \-y install tclx \\ | | libXShm \\ | libXext-devel \\ | yum \-y install libXext-devel | | libbz2 | bzip2-devel \\ | yum \-y install bzip2-devel \\ | | libz \\ | zlib-devel | yum \-y install zlib-devel | | lpng \\ | libpng and libpng-devel \\ | yum \-y install libpng; yum \-y install libpng-devel \\ | | ljpeg \\ | libjpeg and libjpeg-devel \\ | yum \-y install libjpeg; yum \-y install libjpeg-devel | | libavcodec, libavutil, libavformat \\ | ffmpeg and ffmpeg-devel or install from sources \\ | | \\ {noformat}  bunzip2 transcode-xxxxx.tar.bz2 tar xvf transcode-xxxxxx.tar  {noformat}  Then build it: {noformat} cd trancscode-xxxxxxxxx ./configure make sudo make install  {noformat}\\ \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162812 2195580 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the transcode software Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required to make AVED working, if you provid AVED direcly frames, you can go to the next step. Transcode can be install from a RPM using the yum command, but it is not the basic depot boxes, it can be found on the livna depot that you can download at: http://rpm.livna.org/rlowiki/. Download it and install the rpm. Or you can get the code from [http://www.transcoding.org/cgi-bin/transcode]and install it. {noformat}  rpm -ivh livna-release-xxxxx.rpm {noformat}\\ \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162813 2195581 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} {info:title=}Make sure in /opt/condor-xxxxxx/etc/condor_config line reads: DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD {info} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.     Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat} h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ \\ \\ \\ h3.     Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ The web service provided condains the service (src/org/mbari/aved/webservice/server/AvedService.java) and an exemple to request it (src/org/mbari/aved/webservice/client/AvedClient.java). Before deploying the web-service, you have to edit the java code in order to provide the user Condor is gonna run with and the computer sets. For that edit the file AvedService.java in src/org/mbari/aved/webservice/server {noformat} public static String SCHEDD_LOCATION = "http://host.domain.name.org:8181"; public static String USER = "aved"; {noformat} Then, compile the source by tapping {noformat} ant {noformat} If everything is going well, you should see a BUILD SUCCESSFULL printed, and a build folder should have been created. In these folder you'll find a AvedService.aar file what is the web-service \! To deploy it, just copy and past this file into your application server directory, and the jars from the jars into the application server lib directory: {noformat} cp build/AvedService.aar /webapps/axis2/WEB-INF/services/ cp jars/*.jar /webapps/axis2/WEB-INF/lib/ {noformat} Restart tomcat, and check with your browser if your web-service is up by tapping [http://host:8080/axis2/services/listServices], AvedService should be listed. The AVED web-service requires 4 envirenmental variables: {noformat} export MBARIVISIONROOT= export JAVA_HOME= export CONDOR_CONFIG=/opt/condor-xxxxxxxxx/etc/condor_config export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} You can know test it with the client code provided \! \\ The web service is composed of 3 functions:             - OMElement sendJobToAved (String path): this function takes for parameter the path of the video to be processed and return an XML file with node1=the cluster number and node2=the job number             - OMElement getJobStatus (int cluster, int job): this function takes the cluster number and the job number and return the job status (1: Idle, 2:Running, 3:Removed, 4:Completed, 5:Held).             - OMElement getResult (int cluster, int job): this function takes the cluster number and the job number and return the XML result of the processing. The web service client is basicly a java code what send a job to AVED wait until the status id is at 4 (completed) and get the result. \\ \\ h3.     Installing the AVED web-service as a service on Linux * Create tomcat.sh file in /etc/profile.d then add the following to it: {noformat} export JAVA_HOME= export MBARIVISIONROOT= export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} * Create tomcat file in /etc/init.d then add the following to it: {noformat} . /etc/profile.d/tomcat.sh /bin/catalina.sh start {noformat} \* Add soft links to the tomcat startup script {noformat} ln -s /etc/init.d/tomcat /etc/rc2.d/S100tomcat ln -s /etc/init.d/tomcat /etc/rc2.d/K100tomcat {noformat} Start the tomcat service \\ {noformat} service tomcat start {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 2162814 2195582 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} {info:title=}Make sure in /opt/condor-xxxxxx/etc/condor_config line reads: DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD {info} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat} h3.     Configuring Condor Change the following value in the /opt/condor-xxxxxxx/local.xxxxxx/condor_config.local {noformat} ##  When is this machine willing to start a job? START = TRUE ##  When to suspend a job? SUSPEND = FALSE ##  When to nicely stop a job? ##  (as opposed to killing it instantaneously) PREEMPT = FALSE ##  When to instantaneously kill a preempting job ##  (e.g. if a job is in the pre-empting stage for too long) KILL = FALSE {noformat} h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.     Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat} h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ \\ \\ \\ \\ h3.     Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ The web service provided condains the service (src/org/mbari/aved/webservice/server/AvedService.java) and an exemple to request it (src/org/mbari/aved/webservice/client/AvedClient.java). Before deploying the web-service, you have to edit the java code in order to provide the user Condor is gonna run with and the computer sets. For that edit the file AvedService.java in src/org/mbari/aved/webservice/server {noformat} public static String SCHEDD_LOCATION = "http://host.domain.name.org:8181"; public static String USER = "aved"; {noformat} Then, compile the source by tapping {noformat} ant {noformat} If everything is going well, you should see a BUILD SUCCESSFULL printed, and a build folder should have been created. In these folder you'll find a AvedService.aar file what is the web-service \! To deploy it, just copy and past this file into your application server directory, and the jars from the jars into the application server lib directory: {noformat} cp build/AvedService.aar /webapps/axis2/WEB-INF/services/ cp jars/*.jar /webapps/axis2/WEB-INF/lib/ {noformat} Restart tomcat, and check with your browser if your web-service is up by tapping [http://host:8080/axis2/services/listServices], AvedService should be listed. The AVED web-service requires 4 envirenmental variables: {noformat} export MBARIVISIONROOT= export JAVA_HOME= export CONDOR_CONFIG=/opt/condor-xxxxxxxxx/etc/condor_config export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} You can know test it with the client code provided \! \\ The web service is composed of 3 functions:             - OMElement sendJobToAved (String path): this function takes for parameter the path of the video to be processed and return an XML file with node1=the cluster number and node2=the job number             - OMElement getJobStatus (int cluster, int job): this function takes the cluster number and the job number and return the job status (1: Idle, 2:Running, 3:Removed, 4:Completed, 5:Held).             - OMElement getResult (int cluster, int job): this function takes the cluster number and the job number and return the XML result of the processing. The web service client is basicly a java code what send a job to AVED wait until the status id is at 4 (completed) and get the result. \\ \\ h3.     Installing the AVED web-service as a service on Linux * Create tomcat.sh file in /etc/profile.d then add the following to it: {noformat} export JAVA_HOME= export MBARIVISIONROOT= export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} * Create tomcat file in /etc/init.d then add the following to it: {noformat} . /etc/profile.d/tomcat.sh /bin/catalina.sh start {noformat} \* Add soft links to the tomcat startup script {noformat} ln -s /etc/init.d/tomcat /etc/rc2.d/S100tomcat ln -s /etc/init.d/tomcat /etc/rc2.d/K100tomcat {noformat} Start the tomcat service \\ {noformat} service tomcat start {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 2162815 2195556 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162789 2195555 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162788 2195558 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin  {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162791 2195557 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162790 2195560 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your classpath h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162793 2195559 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./configure --enable-shared --prefix=/usr gmake sudo gmake install  {noformat} h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162792 2195562 {noformat}\\ h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ \\ \\ h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162795 2195561 {noformat}\\ h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ \\ h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it:\\ {noformat} condor_reconfig {noformat}\\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162794 2195564 {noformat}\\ h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ \\ \\ \\ \\ h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162797 2195563 {noformat}\\ h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ \\ \\ \\ h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162796 2195566 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ \\ \\ \\ \\ \\ \\ h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ \\ \\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162799 2195565 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ \\ \\ \\ \\ \\ h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ \\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162798 2195568 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} {info:title=}Make sure in /opt/condor-xxxxxx/etc/condor_config line reads: DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD {info} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat} \\ h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162801 2195567 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} {info:title=}Make sure in /opt/condor-xxxxxx/etc/condor_config line reads: DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD {info} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat}\\ \\ \\ \\ \\ \\ \\ \\ h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ \\ \\ \\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.]]> 2162800 2195570 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} {info:title=}Make sure in /opt/condor-xxxxxx/etc/condor_config line reads: DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD {info} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.     Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat} \\ h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ \\ h3.     Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ \\ \\ \\ \\ \\ h3.     Installing the AVED web-service as a service on Linux * Create tomcat.sh file in /etc/profile.d then add the following to it: {noformat} export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install tomcat service script to execute tomcat and deploy the AVED web-service on bootup {noformat} . /etc/profile.d/tomcat.sh {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the tomcat startup script {noformat} ln -s /etc/init.d/tomcat /etc/rc2.d/S100tomcat ln -s /etc/init.d/tomcat /etc/rc2.d/K100tomcat {noformat} Start the condor service {noformat} service tomcat start {noformat}\\ \\ \\ \\]]> 2162803 2195569 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} {info:title=}Make sure in /opt/condor-xxxxxx/etc/condor_config line reads: DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD {info} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat}\\ \\ \\ h3.     Configuring condor \----------------------------------------------\- TODO \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.    Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat} \\ h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ h3.    Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service.\\ \\ \\ \\ \\ \\ h3.     Installing the AVED web-service as a service on Linux * Create tomcat.sh file in /etc/profile.d then add the following to it: {noformat} export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install tomcat service script to execute tomcat and deploy the AVED web-service on bootup {noformat} . /etc/profile.d/tomcat.sh {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the tomcat startup script {noformat} ln -s /etc/init.d/tomcat /etc/rc2.d/S100tomcat ln -s /etc/init.d/tomcat /etc/rc2.d/K100tomcat {noformat} Start the condor service {noformat} service tomcat start {noformat}\\ \\ \\]]> 2162802 2195481 2162714 10388480 10355754 2195482 2162715 10388479 10355753 2195479 2162712 2195480 2162713 2195477 2162710 2195478 2162711 2195476 2162709 10388477 10355751 2195489 2162722 2195490 cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat}\\ \\ \\ \\ \\]]> 2162723 10388471 10355745 2195487 2162720 10388473 10355747 2195485 cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread  ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install  {noformat}\\ \\ \\]]> 2162718 2195486 cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat}\\ \\ \\ \\]]> 2162719 2195483 2162716 2195484 2162717 10388469 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}. {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h3. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 10355743 10388456 10355729 10388452 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default; of course you can change that with the usual {{\--prefix}} argument to {{configure}}. {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h3. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 10355725 10388454 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default; of course you can change that with the usual {{\--prefix}} argument to {{configure}}. {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h3. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 10355727 11273269 11240537 2195511 cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat}\\ \\ \\ h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162744 10388450 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default; of course you can change that with the usual {{\--prefix}} argument to {{configure}}. {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h3. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 10355723 13172782 cp make install mpeg_encode /usr/local/bin {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision and AVED scripts|mbarivision Installation - Step 6. Build and Install mbarivision or pmbarivision]. \\ \\ \\ \\ \\ \\ \\]]> 13140014 2195512 cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat}\\ \\ \\ \\ h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162745 11273267 11240535 2195513 cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat} \\ \\ \\ h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162746 10388448 make install mpeg_encode /usr/local/bin {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision and AVED scripts|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts]. \\ \\ \\ \\ \\ \\ \\]]> 10355721 2195514 cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat} \\ \\ \\ h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162747 11273273 11240545 2195507 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | h3.    Samples  On mbarivision/samples a movie file composed of several frame is provided. The command line exemple are executed from the mbarivision directory. \\ || Goal || Command || Outputs || Comments || | Process a video | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=none \--input-frames=0-99@1 \\ | none \\ | There are several options here. The \--in option says to take input from the named raster file; we support several raster file formats, including png and pnm (ppm/pgm/pbm). The \--out option says we don't want any outputs. When you pass the filename to \--in, put a '#' in the place where the frame number should go. Thus, it will read frame000000.png, frame000001.png. By default, it will keep reading input files until it encounters a missing raster file. If you want it to stop sooner, you can specify a frame range with the \--input-frames option, such as \--input-frames=0-99@1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | \\ | h1. Using the web-service  \\ h1. Using the Graphical User Interface \\ \\]]> 2162740 13172786 cp make install mpeg_encode /usr/local/bin {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision and AVED scripts|mbarivision Installation - Step 6. Build and Install mbarivision or pmbarivision]. \\ \\ \\ \\ \\ \\ \\]]> 13140018 2195508 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | h3.    Exemples  On mbarivision/samples a movie file composed of several frame is provided. The command line exemple are executed from the mbarivision directory. \\ || Goal || Command || Outputs || Comments || | Process a video | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=none \--input-frames=0-99@1 \\ | none \\ | There are several options here. The \--in option says to take input from the named raster file; we support several raster file formats, including png and pnm (ppm/pgm/pbm). The \--out option says we don't want any outputs. When you pass the filename to \--in, put a '#' in the place where the frame number should go. Thus, it will read frame000000.png, frame000001.png. By default, it will keep reading input files until it encounters a missing raster file. If you want it to stop sooner, you can specify a frame range with the \--input-frames option, such as \--input-frames=0-99@1. | | Get a bench of pictures with the events outlined\\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-save-output | Bench of pictures\\ | Same than the previous exemple, but this time the output will be a bench of franes with the events detected outlined by a boundery box.\\ | | Get focussed on benthic animals and save the result into an XML file\\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-cache-size=15 \--mbari-tracking-mode=BoundingBox \--mbari-min-event-area=100 \--mbari-max-event-area=10000 \--mbari-save-events-xml=./benthic.xml\\ | XML file\\ | The tracking mode BoudingBox is using a tracking algorithm which superpose segmentation results. As benthic objects are quite big, we delimited the objects value between \[100-1000\]. The result file is provided in the samples folder as benthic.xml. | h1. Using the web-service  \\ h1. Using the Graphical User Interface \\ \\]]> 2162741 10388445 make install mpeg_encode /usr/local/bin {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision and AVED scripts|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts].\\ \\ \\ \\ \\ \\ \\]]> 10355718 11273271 11240543 2195509 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | h3.    Exemples  On mbarivision/samples a movie file composed of several frame is provided. The command line exemple are executed from the mbarivision directory. \\ || Goal || Command || Outputs || Comments || | Process a video | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=none \--input-frames=0-99@1 \\ | none \\ | There are several options here. The \--in option says to take input from the named raster file; we support several raster file formats, including png and pnm (ppm/pgm/pbm). The \--out option says we don't want any outputs. When you pass the filename to \--in, put a '#' in the place where the frame number should go. Thus, it will read frame000000.png, frame000001.png. By default, it will keep reading input files until it encounters a missing raster file. If you want it to stop sooner, you can specify a frame range with the \--input-frames option, such as \--input-frames=0-99@1. | | Get a bench of pictures with the events outlined \\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-save-output | Bench of pictures \\ | Same than the previous exemple, but this time the output will be a bench of franes with the events detected outlined by a boundery box. \\ | | Get focussed on benthic animals and save the result into an XML file \\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-cache-size=15 \--mbari-tracking-mode=BoundingBox \--mbari-min-event-area=100 \--mbari-max-event-area=10000 \--mbari-save-events-xml=./benthic.xml \\ | XML file \\ | The tracking mode BoudingBox is using a tracking algorithm which superpose segmentation results. As benthic objects are quite big, we delimited the objects value between \[100-1000\]. The result file is provided in the samples folder as benthic.xml. | h1. Using the Graphical User Interface So far, the graphical usr interface is not available, but it will be in the release of next year. \\ \\]]> 2162742 13172784 cp make install mpeg_encode /usr/local/bin {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision and AVED scripts|mbarivision Installation - Step 6. Build and Install mbarivision or pmbarivision]. \\ \\ \\ \\ \\ \\ \\]]> 13140016 2195510 cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat}\\ \\ h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162743 10388443 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is diminishing, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue to the next optional step [AVED Installation - Step 5. Build and install Berkeley MPEG Encoder|AVED:AVED Installation - Step 5. Build and install Berkeley MPEG Encoder (optional)]\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 10355716 2195519 2162752 10388442 10355715 2195520 2162753 10388441 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P=/usr/local gmake sudo gmake install {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} Install the XML::Xerces library {noformat} export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software].]]> 10355714 2195521 cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat} h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162754 10388440 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P=/usr/local gmake sudo gmake install {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} Install the XML::Xerces library {noformat} export XERCES_LIB=/usr/local/ib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software].]]> 10355713 2195522 2162755 2195515 cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat} \\ \\ \\ h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 2162748 10388438 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to tinker with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 10355711 2195516 2162749 10388437 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to tinker with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 10355710 2195517 2162750 2195518 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | h3.    Exemples  On mbarivision/samples a movie file composed of several frame is provided. The command line exemple are executed from the mbarivision directory. \\ || Goal || Command || Outputs || Comments || | Process a video | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=none \--input-frames=0-99@1 \\ | none \\ | There are several options here. The \--in option says to take input from the named raster file; we support several raster file formats, including png and pnm (ppm/pgm/pbm). The \--out option says we don't want any outputs. When you pass the filename to \--in, put a '#' in the place where the frame number should go. Thus, it will read frame000000.png, frame000001.png. By default, it will keep reading input files until it encounters a missing raster file. If you want it to stop sooner, you can specify a frame range with the \--input-frames option, such as \--input-frames=0-99@1. | | Get a bench of pictures with the events outlined \\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-save-output | Bench of pictures \\ | Same than the previous exemple, but this time the output will be a bench of franes with the events detected outlined by a boundery box. \\ | | Get focussed on benthic animals and save the result into an XML file \\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-cache-size=15 \--mbari-tracking-mode=BoundingBox \--mbari-min-event-area=100 \--mbari-max-event-area=10000 \--mbari-save-events-xml=./benthic.xml \\ | XML file \\ | The tracking mode BoudingBox is using a tracking algorithm which superpose segmentation results. As benthic objects are quite big, we delimited the objects value between \[100-1000\]. The result file is provided in the samples folder as benthic.xml. | h1.  Using the scripts \--------------------------------------\- TODO  h1. Using the Graphical User Interface So far, the graphical usr interface is not available, but it will be in the release of next year. \\ \\]]> 2162751 2195496 x | default \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | \\ \\ \\ \\ \\ \\ | h1. Using the Graphical User Interface For now, the user interface is not available, but a release coming begining of next year should come with a GUI.  h1. Using the web-service ]]> 2162729 2195495 x | default \[0x0\]\\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |\\ \\ \\ \\ \\ \\ h1. Using the Graphical User Interface For now, the user interface is not available, but a release coming begining of next year should come with a GUI.  h1. Using the web-service ]]> 2162728 2195498 x | default \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | \\ \\ \\ \\ \\ \\ | h1. Using the Graphical User Interface For now, the user interface is not available, but a release coming begining of next year should come with a GUI.  h1. Using the web-service ]]> 2162731 2195497 x | default \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | \\ \\ \\ \\ \\ \\ | h1. Using the Graphical User Interface For now, the user interface is not available, but a release coming begining of next year should come with a GUI.  h1. Using the web-service ]]> 2162730 13172801 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now, go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|mbarivision Installation - Step 2. Build and Install XML Libraries]]]> 13140035 2195491 cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread ./configure --enable-shared --prefix=/usr/local gmake sudo gmake install {noformat}\\ h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat}  ./configure {noformat} You can add the parameter ./configure --help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\ h1. Install Condor to manage AVED workflow  \\]]> 2162724 13172800 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now, go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|mbarivision Installation - Step 2. Build and Install XML Libraries]]]> 13140034 2195494 2162727 2195493 2162726 2195504 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | h1. Using the Graphical User Interface For now, the user interface is not available, but a release coming begining of next year should come with a GUI.  h1. Using the web-service ]]> 2162737 2195503 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events\\ | \[yes\]\\ | If saving events, save only the interesting events\\ | | \--mbari-save-events-xml=fileName \\ | \[\]\\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\]\\ | Add video input source information to XML output\\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode=\\ | \[KalmanFilter\]\\ | Way to mark interesting events in output of MBARI programs\\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\]\\ | Segmentation algorithm\\ | | \--mbari-mask-path=\\ | \[\]\\ | MaskPath: path to the mask image\\ | | \--mbari-mask-xposition= | \[1\]\\ | MaskXPosition: x position of the mask point of reference\\ | | \--mbari-mask-yposition=\\ | \[1\] | MaskYPosition: y position of the mask point of reference\\ | | \--mbari-mask-width=\\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height=\\ | \[1\] | MaskHeight: mask height\\ | | \--mbari-min-event-area= | \[34\]\\ | The minimum area an event must be to be candidate\\ | | \--mbari-max-event-area=\\ | \[1000\]\\ | The maximum area an event can be, to be candidate\\ | h1. Using the Graphical User Interface For now, the user interface is not available, but a release coming begining of next year should come with a GUI.  h1. Using the web-service ]]> 2162736 2195506 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | h3.    Samples  On mbarivision/samples a movie file composed of several frame is provided. The command line exemple are executed from the mbarivision directory. \\ || Goal || Command || Outputs || Comments || | Process a video | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=none \--input-frames=0-99@1\\ | none \\ | There are several options here. The \--in option says to take input from the named raster file; we support several raster file formats, including png and pnm (ppm/pgm/pbm). The \--out option says we don't want any outputs. When you pass the filename to \--in, put a '#' in the place where the frame number should go. Thus, it will read frame000000.png, frame000001.png. By default, it will keep reading input files until it encounters a missing raster file. If you want it to stop sooner, you can specify a frame range with the \--input-frames option, such as \--input-frames=0-99@1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |\\ h1. Using the web-service  \\ h1. Using the Graphical User Interface \\ \\]]> 2162739 13172787 cp make install mpeg_encode /usr/local/bin {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision and AVED scripts|mbarivision Installation - Step 6. Build and Install mbarivision or pmbarivision]. \\ \\ \\ \\ \\ \\ \\]]> 13140019 2195505 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | h1. Using the Graphical User Interface For now, the user interface is not available, but a release coming begining of next year should come with a GUI.  h1. Using the web-service ]]> 2162738 2195500 x | default \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | default \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | default \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | This parameter is required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | | | | | *Output Writng/Formatting* | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | \\ \\ \\ \\ \\ \\ | h1. Using the Graphical User Interface For now, the user interface is not available, but a release coming begining of next year should come with a GUI.  h1. Using the web-service ]]> 2162733 2195499 x | default \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | --\[no\]preserve-input-aspect \\ | default \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims\\ | | --zero-number-frames= | default \[false\]\\ | Force all input and output frames to have the number 000000 | | --in=<\[type\]:\[spec\]> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | \\ \\ \\ \\ \\ \\ | h1. Using the Graphical User Interface For now, the user interface is not available, but a release coming begining of next year should come with a GUI.  h1. Using the web-service ]]> 2162732 2195502 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName\\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | --mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\]\\ | Write event labels into the output frames\\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling\\ | | \--mbari-save-events=fileName | \[\]\\ | Save the event structure to a text file\\ | | \--mbari-save-properties=fileName\\ | \[\]\\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName\\ | \[\]\\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\]\\ | Save video clips showing specific events | | \\ | \\ | \\ | | | | | | | | | | *Special Features* | | | | --mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | | | | | | | | | | | | h1. Using the Graphical User Interface For now, the user interface is not available, but a release coming begining of next year should come with a GUI.  h1. Using the web-service ]]> 2162735 2195501 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | | | | | *Output Writng/Formatting* | | | | \--out= | required\\ | Value recomended is none.\\ | | \--\[no\]mbari-save-results\\ | \[no\]\\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate\\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction\\ | \[no\]\\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs\\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | | | | | | | | \\ \\ \\ \\ \\ \\ | h1. Using the Graphical User Interface For now, the user interface is not available, but a release coming begining of next year should come with a GUI.  h1. Using the web-service ]]> 2162734 9404552 cd $XERCESCROOT/src/xerces runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [][AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software (optional)]]]> 9371800 9404551 cd $XERCESCROOT/src/xerces runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation - Step 3. Build and Install Transcode Software]]]> 9371798 9404554 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is diminishing, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue to the next optional step [AVED Installation - Step 5. Build and install Berkeley MPEG Encoder]\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 9371804 9404553 9371802 9404547 ./configure make make install {noformat}\\ \\ \\ \\ \\ \\]]> 9371792 11829540 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796783 11829543 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796786 11829545 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. Setup the user profile Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. Configure ssh Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796788 11829546 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. Setup the user profile Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. Configure ssh Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796789 11829563 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796806 11829555 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796798 11829558 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796801 11829557 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796800 11829561 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796804 5407448 5374717 28 20 717 2007-02-14 14:02:31.110 2007-02-14 14:02:31.110 11829518 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/ {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796761 11829515 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/ {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd.conf {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796758 11829516 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/ {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd.conf {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796759 11829521 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796764 11829522 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796765 11829520 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/ {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796763 11829509 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/ {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd.conf {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service ssh restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796752 11829510 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/ {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd.conf {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service ssh restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796753 11829508 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/ {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd.conf {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc {noformat} h2. SSH configuration Add to /etc/ssh/ssh_config, then restart the service Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796751 11829513 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/ {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd.conf {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service ssh restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796756 11829514 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/ {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd.conf {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service ssh restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796757 11829511 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/ {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd.conf {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service ssh restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796754 5407431 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed to use. Passwords for both the root and aved users have been sent to Dhugal. Two additional steps were required for this installation: # Add manual links for the dc1394 control libraries. This was needed to get saliency to compile. {noformat} cd /usr/lib ln -s libdc1394.so.22 libdc1394_control.so ln -s libdc1394.so.22 libdc1394.so {noformat} # Add /usr/local/lib to the /etc/ld.so.conf. This was needed to get the loader to load the dependent libraries (e.g. xercesc) that are by default installed to /usr/local/lib to load. {noformat} echo /usr/local/lib >> /etc/ld.so.conf {noformat}\\ \\ h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139Z.mov \\ | {tip:title=Handy Hint}This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]\\ date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number. \\ E.g. 20080604T063139Z assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} \\ \| Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. \\ \\ \| cd /home/aved/Video/20080604T063139Z.mov; jamstec_runprocess 20080604T063139Z.mov \| h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 5374700 11829533 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796776 5407433 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed to use. Passwords for both the root and aved users have been sent to Dhugal. Two additional steps were required for this installation: # Add manual links for the dc1394 control libraries. This was needed to get saliency to compile. {noformat} cd /usr/lib ln -s libdc1394.so.22 libdc1394_control.so ln -s libdc1394.so.22 libdc1394.so {noformat} # Add /usr/local/lib to the /etc/ld.so.conf. This was needed to get the loader to load the dependent libraries (e.g. xercesc) that are by default installed to /usr/local/lib to load. {noformat} echo /usr/local/lib >> /etc/ld.so.conf {noformat}\\ \\ h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a\\ jamstec_runmbarivis_displayalg\\ \\ This will display output, similar to the following. \*NOTE\* Windows display overlapped, not in the cascade pattern shown in this image. Just remember to click and drag them from on top of each other.\\ (click to enlarge)  !ScreenshotAlgorithmRunning.png|thumbnail!\\ \\ OR \\ jamstec_runmbarivis \\ This will simply spew out the output from mbarivision into the console window. \\ (click to enlarge)  !ScreenshotJamstecrunmbarivis.png|thumbnail!\\ \\ | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect\\ jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139Z.mov \\ | {tip:title=Handy Hint}This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]\\ date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number. \\ E.g. 20080604T063139Z assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} \\ \| Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. \\ \\ \| cd /home/aved/Video/20080604T063139Z.mov; jamstec_runprocess 20080604T063139Z.mov \| h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 5374702 11829531 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796774 11829537 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796780 11829535 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796778 11829526 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796769 11829524 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796767 5407441 cd src/xerces runConfigure -p linux gmake sudo gmake install {noformat} {color:#990000}TODO: Verify this - is this for mbarivision ? make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib){color} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat}]]> 5374710 11829523 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796766 5407442 cd src/xerces runConfigure -p linux gmake sudo gmake install {noformat} {color:#990000}TODO: Verify this - is this for mbarivision ? make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib){color} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat}]]> 5374711 5407435 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed to use. Passwords for both the root and aved users have been sent to Dhugal. Two additional steps were required for this installation: # Add manual links for the dc1394 control libraries. This was needed to get saliency to compile. {noformat} cd /usr/lib ln -s libdc1394.so.22 libdc1394_control.so ln -s libdc1394.so.22 libdc1394.so {noformat} # Add /usr/local/lib to the /etc/ld.so.conf. This was needed to get the loader to load the dependent libraries (e.g. xercesc) that are by default installed to /usr/local/lib to load. {noformat} echo /usr/local/lib >> /etc/ld.so.conf {noformat}\\ \\ h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a \\ jamstec_runmbarivis_displayalg \\ \\ This will display output, similar to the following. \*NOTE\* Windows display overlapped, not in the cascade pattern shown in this image. Just remember to click and drag them from on top of each other. \\ (click to enlarge)  !ScreenshotAlgorithmRunning.png|thumbnail!\\ \\ OR \\ jamstec_runmbarivis  \\ This will simply spew out the output from mbarivision into the console window.  \\ (click to enlarge)  !ScreenshotJamstecrunmbarivis.png|thumbnail!\\ \\ | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect \\ jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139Z.mov \\ | {tip:title=Handy Hint}This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]\\ date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number. \\ E.g. 20080604T063139Z assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} \\ \| Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. \\ \\ \| cd /home/aved/Video/20080604T063139Z.mov; jamstec_runprocess 20080604T063139Z.mov \| h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 5374704 11829529 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796772 5407436 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed to use. Passwords for both the root and aved users have been sent to Dhugal. Two additional steps were required for this installation: # Add manual links for the dc1394 control libraries. This was needed to get saliency to compile. {noformat} cd /usr/lib ln -s libdc1394.so.22 libdc1394_control.so ln -s libdc1394.so.22 libdc1394.so {noformat} # Add /usr/local/lib to the /etc/ld.so.conf. This was needed to get the loader to load the dependent libraries (e.g. xercesc) that are by default installed to /usr/local/lib to load. {noformat} echo /usr/local/lib >> /etc/ld.so.conf {noformat}\\ \\ h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a \\ jamstec_runmbarivis_displayalg \\ \\ This will display output, similar to the following. \*NOTE\* Windows display overlapped, not in the cascade pattern shown in this image. Just remember to click and drag them from on top of each other. \\ (click to enlarge)  !ScreenshotAlgorithmRunning.png|thumbnail!\\ \\ OR \\ jamstec_runmbarivis  \\ This will simply spew out the output from mbarivision into the console window.  \\ (click to enlarge)  !ScreenshotJamstecrunmbarivis.png|thumbnail!\\ \\ | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect \\ jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139Z.mov \\ {tip:title=Handy Hint}This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]\\ date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number. \\ E.g. 20080604T063139Z assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} | Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. | cd /home/aved/Video/20080604T063139Z.mov; jamstec_runprocess 20080604T063139Z.mov \| | h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 5374705 11829528 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. SSH configuration Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796771 5407438 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed to use. Passwords for both the root and aved users have been sent to Dhugal. Two additional steps were required for this installation: # Add manual links for the dc1394 control libraries. This was needed to get saliency to compile. {noformat} cd /usr/lib ln -s libdc1394.so.22 libdc1394_control.so ln -s libdc1394.so.22 libdc1394.so {noformat} # Add /usr/local/lib to the /etc/ld.so.conf. This was needed to get the loader to load the dependent libraries (e.g. xercesc) that are by default installed to /usr/local/lib to load. {noformat} echo /usr/local/lib >> /etc/ld.so.conf {noformat}\\ \\ h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a \\ jamstec_runmbarivis_displayalg \\ \\ This will display output, similar to the following. \*NOTE\* Windows display overlapped, not in the cascade pattern shown in this image. Just remember to click and drag them from on top of each other. \\ (click to enlarge)  !ScreenshotAlgorithmRunning.png|thumbnail!\\ \\ OR \\ jamstec_runmbarivis  \\ This will simply spew out the output from mbarivision into the console window.  \\ (click to enlarge)  !ScreenshotJamstecrunmbarivis.png|thumbnail!\\ \\ | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect \\ jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139Z.mov \\ {tip:title=Handy Hint}This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]\\ date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number. \\ E.g. 20080604T063139Z assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} | Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. | cd /home/aved/Video/20080604T063139Z.mov; jamstec_runprocess 20080604T063139Z.mov\\ | h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 5374707 11829612 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. Setup the user profile Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. Configure ssh Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796854 11829631 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. Setup the user profile Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd service similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. This is used to configure a mpd ring running under the root account that will be used by users. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. Configure ssh Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796873 11829633 11796875 11829628 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. Setup the user profile Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. Configure ssh Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796870 11829630 11796872 6225957 6258728 6225958 ./bootstrap ./configure make sudo make install {noformat} h3. Linux \\ {noformat} cd ./configure make sudo make install {noformat}\\ \\ \\ \\]]> 6258729 6225955 6258726 6225962 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track. We did this primarily because we found the OpenQuicktime library could be modified to add a timecode track which we synchronized with the timecode track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks,  was added to the Quicktime tracks in early AVED development. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We no longer support OpenQuicktime timecode tracks, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] standard, and then maintain the timecode track in the xml formatted results of the output. Also, OpenQuicktime is not supported by the transcoding software, therefore the preferred tool used by the transcoding software is simply the quicktime library (for Linux), and instructions for it are noted below. h3. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. Check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: {noformat} cd ./configure make sudo make install {noformat}\\ \\ \\ \\ \\]]> 6258733 6225960 ./configure make sudo make install {noformat} h3. Building and Installing Quicktime The preferred tool used by the transcoding software is simply Quicktime (for Linux). Download it from here and install: [http://libquicktime.sourceforge.net/][http://libquicktime.sourceforge.net/] \\ {noformat} cd ./configure make sudo make install {noformat}\\ \\ \\ \\ \\]]> 6258731 6225964 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexbility in the video containers and since support for OpenQuicktime is waning abandoning it was logical. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. Check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: {noformat} cd ./configure make sudo make install {noformat}\\ \\ \\ \\ \\ \\]]> 6258735 11829638 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. Setup the user profile Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd service similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. This is used to configure a mpd ring running under the root account that will be used by users. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. Configure ssh Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} push /usr/lib/libavcodec.so.51 /usr/lib/ cpush /usr/lib/libavcodec.so.52 /usr/lib/ cpush /usr/lib/libavcodec.so.52 /usr/lib/ cpush /usr/lib/libavcodec.so.51.40.4 /usr/lib/ cpush /usr/lib/libavformat.so.51.12.1 /usr/lib cpush /usr/lib/libavformat.so.51 /usr/lib cpush /usr/lib/libavformat.so.51.12.1 /usr/lib cpush /usr/lib/libavformat.so.51.12.1 /usr/lib/ cpush /usr/lib/libavformat.so.51.12.1 cpush /usr/lib/libavutil.so.*.* /usr/lib/ cpush /usr/lib/libavutil.so.* /usr/lib cpush /usr/lib/libavutil.so /usr/lib cexec 'ldconfig' cexec 'ldconfig' {noformat}]]> 11796880 6225924 6258691 11829636 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. Setup the user profile Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd service similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. This is used to configure a mpd ring running under the root account that will be used by users. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. Configure ssh Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.* /usr/lib/ cpush /usr/lib/libavformat.so.* /usr/lib cpush /usr/lib/libavutil.so.* /usr/lib/ cexec 'ldconfig' {noformat}]]> 11796878 6225926 6258694 6225927 6258695 14549035 14516268 11829640 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. Setup the user profile Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd service similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. This is used to configure a mpd ring running under the root account that will be used by users. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. Configure ssh Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.51 cpush /usr/lib/libavcodec.so.52 cpush /usr/lib/libavcodec.so.51.40.4 cpush /usr/lib/libavformat.so.51.12.1 cpush /usr/lib/libavformat.so.51 cpush /usr/lib/libavformat.so.51.12.1 cpush /usr/lib/libavutil.so.*.* cpush /usr/lib/libavutil.so.* cpush /usr/lib/libavutil.so cexec 'ldconfig' {noformat}]]> 11796882 6225929 6258697 6225931 6258699 6225932 6258700 6225934 6258702 11829649 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. Setup the user profile Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd service similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. This is used to configure a mpd ring running under the root account that will be used by users. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. Configure ssh Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.51 cpush /usr/lib/libavcodec.so.52 cpush /usr/lib/libavcodec.so.51.40.4 cpush /usr/lib/libavformat.so.51.12.1 cpush /usr/lib/libavformat.so.51 cpush /usr/lib/libavformat.so.51.12.1 cpush /usr/lib/libavutil.so cpush /usr/lib/libavutil.so.49 cpush /usr/lib/libavutil.so.49.4.0 cpush /usr/lib/libSDL-1.2.so.0 cpush /usr/lib/libSDL-1.2.so.0.7.0 cexec 'ldconfig' {noformat}]]> 11796891 6225936 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h2. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have compiled over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 6258704 6225937 ./configure make make install {noformat}\\ \\ \\ \\ \\]]> 6258707 11829653 11796895 11829654 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796896 6225942 6258713 11829652 11796894 11829657 11796902 6225944 6258715 11829655 11796898 6225946 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h2. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have compiled over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 6258717 11829656 11796900 11829661 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. Setup the user profile Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd service similar to the following in etc/rc.d/init.d/mpd. This assumes you have 4 CPUs per each node. This is used to configure a mpd ring running under the root account that will be used by users. {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} h2. Start the MPD service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. Configure ssh Add the following to /etc/ssh/ssh_config, Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no then restart the service {noformat} service sshd restart {noformat} h2. Copy library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.51 cpush /usr/lib/libavcodec.so.52 cpush /usr/lib/libavcodec.so.51.40.4 cpush /usr/lib/libavformat.so.51.12.1 cpush /usr/lib/libavformat.so.51 cpush /usr/lib/libavformat.so.51.12.1 cpush /usr/lib/libavutil.so cpush /usr/lib/libavutil.so.49 cpush /usr/lib/libavutil.so.49.4.0 cpush /usr/lib/libSDL-1.2.so.0 cpush /usr/lib/libSDL-1.2.so.0.7.0 cexec 'ldconfig' {noformat}]]> 11796906 6225948 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h2. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have compiled over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 6258719 11829659 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796904 6225950 ./bootstrap ./configure --prefix=/usr/local make make install {noformat}]]> 6258721 6225952 ./bootstrap ./configure make make install {noformat} h3. Linux \\ {noformat} cd ./configure make make install {noformat}\\ \\]]> 6258723 6225951 ./bootstrap ./configure --prefix=/usr/local make make install {noformat} h3. Linux {noformat} cd ./configure --prefix=/usr/local make make install {noformat}\\]]> 6258722 6225953 ./bootstrap ./configure make make install {noformat} h3. Linux \\ {noformat} cd ./configure make make install {noformat}\\ \\ \\]]> 6258724 10388687 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P /usr/local gmake sudo gmake install {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} Install the XML::Xerces library {noformat} export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software].]]> 10355961 10388689 10355963 10388690 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P /usr/local gmake {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} Install the XML::Xerces library {noformat} export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software].]]> 10355964 11829746 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. Add user _aved_ It is recommended to install and run the pmbarivision binary as a user _aved_ that is visible across all nodes. To support this, create a user _aved_ for installing and running pmbarivision. As the _root_ user: {noformat} groupadd -g 300 aved useradd -c "AVED" -g aved -u 300 aved {noformat} The _aved_ user and group id must be synchronized across all nodes and machines in the Beowulf cluster. Once the _aved_ user is created, syncing up the user is typically done automatically by the OSCAR Password Installer and User Management (OPIUM) software, but you can also do this manually with: {noformat} /opt/opium/bin/sync_users -f {noformat} h2. Setup the user profile Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {code:title= /etc/profile.d/aved.csh |borderStyle=solid} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {code} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Configure SSH Add the following to /etc/ssh/ssh_config, {code:title= /etc/ssh/ssh_config |borderStyle=solid} Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no {code} then restart the service {noformat} service sshd restart {noformat} h2. Copy library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.51 cpush /usr/lib/libavcodec.so.52 cpush /usr/lib/libavcodec.so.51.40.4 cpush /usr/lib/libavformat.so.51.12.1 cpush /usr/lib/libavformat.so.51 cpush /usr/lib/libavformat.so.51.12.1 cpush /usr/lib/libavutil.so cpush /usr/lib/libavutil.so.49 cpush /usr/lib/libavutil.so.49.4.0 cpush /usr/lib/libSDL-1.2.so.0 cpush /usr/lib/libSDL-1.2.so.0.7.0 cexec 'ldconfig' {noformat}]]> 11796992 11829742 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. Add user _aved_ It is recommended to install and run the pmbarivision binary as a user _aved_ that is visible across all nodes. To support this, create a user _aved_ for installing and running pmbarivision. As the _root_ user: {noformat} groupadd -g 300 aved useradd -c "AVED" -g aved -u 300 aved {noformat} The _aved_ user and group id must be synchronized across all nodes and machines in the Beowulf cluster. Once the _aved_ user is created, syncing up the user is typically done automatically by the OSCAR Password Installer and User Management (OPIUM) software, but you can also do this manually with: {noformat} /opt/opium/bin/sync_users -f {noformat} h2. Setup the user profile Install aved.sh/csh similar to following in the /etc/profile.d/. Change the MPDIR setting to the appropriate one in your installation. {code:title= /etc/profile.d/aved.csh |borderStyle=solid} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {code} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd service This is used to configure a mpd ring running under the root account that will be used by users. This assumes you have 4 CPUs per each node and you may need to adjust this according to your cluster. # Create mpd service file similar to the following {code:title= /etc/rc.d/init.d/mpd |borderStyle=solid} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=4 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {code} # Then push to the other nodes {noformat} cpush /etc/rc.d/init.d/mpd /etc/rc.d/init.d/mpd {noformat} # Start the mpd service {noformat} service mpd start {noformat} You should see the nodes all come up, something like (not necessarily in this order): {noformat} beowulffish node1 node4 node3 node2 node5 node8 node6 node7 {noformat} h2. Configure SSH Add the following to /etc/ssh/ssh_config, {code:title= /etc/ssh/ssh_config |borderStyle=solid} Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no {code} then restart the service {noformat} service sshd restart {noformat} h2. Copy library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.51 cpush /usr/lib/libavcodec.so.52 cpush /usr/lib/libavcodec.so.51.40.4 cpush /usr/lib/libavformat.so.51.12.1 cpush /usr/lib/libavformat.so.51 cpush /usr/lib/libavformat.so.51.12.1 cpush /usr/lib/libavutil.so cpush /usr/lib/libavutil.so.49 cpush /usr/lib/libavutil.so.49.4.0 cpush /usr/lib/libSDL-1.2.so.0 cpush /usr/lib/libSDL-1.2.so.0.7.0 cexec 'ldconfig' {noformat}]]> 11796988 11829754 11797000 11829750 11796996 11829759 11797005 10388691 10355965 11829760 11797006 10388693 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P /usr/local gmake {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} Install the XML::Xerces library {noformat} export XERCESCROOT= export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software].]]> 10355967 11829762 11797008 10388695 cp make install mpeg_encode /usr/local/bin {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision and AVED scripts|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts]. \\ \\ \\ \\ \\ \\ \\]]> 10355969 11829756 11797002 11829757 11797003 11829758 11797004 10388718 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P /usr/local gmake {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} Install the XML::Xerces library {noformat} export XERCESCROOT= export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} {tip:title=Handy Hint} If you installed the Xerces C+\+ library to a non-standard library location, be sure to add to the loader path in /etc/ld.so.conf the location, and run ldconfig -v to refresh the loader. {tip} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software].]]> 10355992 10388721 10355995 11272964 11240224 10388719 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is diminishing, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue to the next optional step [AVED Installation - Step 5. Build and install Berkeley MPEG Encoder|AVED:AVED Installation - Step 5. Build and install Berkeley MPEG Encoder (optional)]\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 10355993 11272963 11240223 10388720 10355994 9404541 9371786 11829719 11796965 11829720 11796966 9404539 cd $XERCESCROOT/src/xerces runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install   {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat}]]> 9371784 11829717 11796963 9404545 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is diminishing, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat} When done, to complete installation continue to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue to the next optional step [AVED Installation - Step 5. Build and install Berkeley MPEG Encoder] \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 9371790 9404544 9371789 9404543 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is waning, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 9371788 10388724 proxy_password= {noformat} Then install mpeg4ip with: {noformat} yum install mpeg4ip {noformat} If still no luck installing from RPM, see http://mpeg4ip.sourceforge.net/ to instructions on download and installation.]]> 10355998 10388723 proxy_password= {noformat} Then install mpeg4ip with: {noformat} yum install mpeg4ip {noformat} ]]> 10355997 9404537 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the minimal build required for running the AVED software requires that you make _core_ and _tprogs_ with: {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server.]]> 9371782 11829724 11796970 11272958 11240218 11829310 11796545 11272957 11240217 11829309 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed to use. Passwords for both the root and aved users have been sent to Dhugal. Two additional steps were required for this installation: # Add manual links for the dc1394 control libraries. This was needed to get saliency to compile. {noformat} cd /usr/lib ln -s libdc1394.so.22 libdc1394_control.so ln -s libdc1394.so.22 libdc1394.so {noformat} # Add /usr/local/lib to the /etc/ld.so.conf. This was needed to get the loader to load the dependent libraries (e.g. xercesc) that are by default installed to /usr/local/lib to load. {noformat} echo /usr/local/lib >> /etc/ld.so.conf {noformat}\\ \\ h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a \\ jamstec_runmbarivis_displayalg \\ \\ This will display output, similar to the following. \*NOTE\* Windows display overlapped, not in the cascade pattern shown in this image. Just remember to click and drag them from on top of each other. \\ (click to enlarge)  !ScreenshotAlgorithmRunning.png|thumbnail!\\ \\ OR \\ jamstec_runmbarivis  \\ This will simply spew out the output from mbarivision into the console window.  \\ (click to enlarge)  !ScreenshotJamstecrunmbarivis.png|thumbnail!\\ \\ | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect \\ jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139Z.mov \\ {tip:title=Handy Hint}This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]\\ date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number. \\ E.g. 20080604T063139Z assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} | Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. | cd /home/aved/Video/20080604T063139Z.mov; jamstec_runprocess 20080604T063139Z.mov \\ | h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. *This must be executed in the root directory of the ppm frames*, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. *This must be executed in the root directory of the ppm frames*, Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 11796544 11272956 /dev/null 2>&1 #on the first of every month, remove files older than 90 days 00 00 01 * * /usr/local/bin/cleanscratchfiles #at midnight daily rebuild scratch in case new users added or permissions changed 59 23 * * * /usr/local/bin/buildscratch #check disk space every hour and send root alert if getting too full 0 * * * * /usr/local/bin/diskalert {noformat} diskalert {noformat} #!/bin/sh # set -x # Shell script to monitor or watch the disk space # It will send an email to $ADMIN, if the (free available) percentage of space is >= 90%. # ------------------------------------------------------------------------- # Set admin email so that you can get email. ADMIN="root" # set alert level 90% is default ALERT=90 # Exclude list of unwanted monitoring, if several partions then use "|" to separate the partitions. # An example: EXCLUDE_LIST="/dev/hdd1|/dev/hdc5" EXCLUDE_LIST="tempest:/users|tempest:/tempbox:tornado:/Engineering|tornado:/vol/vol1/ProjectLibrary|nanomia.private.net:/nanomiaRAID" # #:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: # function main_prog() { while read output; do #echo $output usep=$(echo $output | awk '{ print $1}' | cut -d'%' -f1) partition=$(echo $output | awk '{print $2}') if [ $usep -ge $ALERT ] ; then echo "Running out of space \"$partition ($usep%)\" on server $(hostname), $(date)" | mail -s "ALERT: Almost out of disk space $usep% on $(hostname)" $ADMIN fi done } if [ "$EXCLUDE_LIST" != "" ] ; then df -lH | grep -vE "^Filesystem|tmpfs|cdrom|${EXCLUDE_LIST}" | awk '{print $5 " " $6}' | main_prog else df -lH | grep -vE "^Filesystem|tmpfs|cdrom" | awk '{print $5 " " $6}' | main_prog fi {noformat} buildscratch {noformat} ! /bin/bash #set -x USERID=`id -u` if [ $USERID != 0 ]; then echo "You must be root to rue buildscratch" exit 0 fi function dowork() { echo "Building $1" #remove all directories and recreate using file containing users users=$(cat /etc/passwd |grep 20| cut -f1 -d ":") pushd /mnt/scratch #change permissions to include all users chmod a+rwx /mnt/scratch #change owner for new directories for dir in $users do if [ ! -d $dir ]; then echo "mkdir $dir" mkdir $dir fi echo "chown $dir:users $dir" chown $dir:users $dir echo "chmod 0777 $dir " chmod 777 $dir done chown aved:aved aved popd #refresh scratch space NFS mounts on all nodes #cexec '/bin/umount /mnt/scratch;/bin/mount /mnt/scratch' } for s in "/mnt/scratch" "/mnt/scratch2" do dowork $s done #rebuild video directories for capture echo "Rebuilding video capture directories" if [ ! -d /mnt/scratch/video ]; then mkdir -p /mnt/scratch/video/capture fi chmod -Rf a+rwx /mnt/scratch/video #rebuild directories for condor if [ ! -d /mnt/scratch/condor ]; then mkdir -p /mnt/scratch/condor -m=0755 fi chown daemon:root /mnt/scratch/condor {noformat}]]> 11240216 11829308 11796543 11829307 11796541 11272962 11240222 11829313 11796550 11272960 11240220 11829312 11796549 11272950 11240210 11829302 11796536 11272948 11240208 11272954 11240214 11829306 11796540 11829305 11796539 11272952 11240212 11829304 11796538 11829303 11796537 11829293 11796526 11272942 11240201 11829294 export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} {tip:title=Handy Hint} If you installed the Xerces C+\+ library to a non-standard library location, be sure to add to the loader path in /etc/ld.so.conf the location, and run ldconfig -v to refresh the loader. {tip} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED Installation - Step 6. Build and Install (p)mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED Installation - Step 3. Build and Install Transcode and mpeg4ip Software].]]> 11796527 11272940 11240199 11829292 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}.If you want the mbarivision to be accessible by all users, example environment settings have been provided to add to your system. For example, on Fedora Linux, add these to /etc/profile.d. You must do this step to setup a machine that will run mbarivision as a Condor node. {noformat} cd cp aved.*sh /etc/profile.d/ {noformat} {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} h3. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 11796525 11829297 cp make install mpeg_encode /usr/local/bin {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision and AVED scripts|AVED Installation - Step 6. Build and Install (p)mbarivision and AVED scripts]. \\ \\ \\ \\ \\ \\ \\]]> 11796530 11272946 11240206 11829298 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} h3. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 11796531 11272943 11240202 11829295 11796528 10388740 10356014 11272944 11240203 11829296 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is diminishing, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat} When you are done, you can skip to [step 6|AVED Installation - Step 6. Build and Install (p)mbarivision and AVED scripts], or continue to the next optional step [AVED Installation - Step 5. Build and install Berkeley MPEG Encoder|AVED:AVED Installation - Step 5. Build and install Berkeley MPEG Encoder (optional)]\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 11796529 11829285 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796518 11272934 11240192 11829286 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796519 11272931 11240189 11829283 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796516 11272932 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation (single node)].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed to use. Passwords for both the root and aved users have been sent to Dhugal. Two additional steps were required for this installation: # Add manual links for the dc1394 control libraries. This was needed to get saliency to compile. {noformat} cd /usr/lib ln -s libdc1394.so.22 libdc1394_control.so ln -s libdc1394.so.22 libdc1394.so {noformat} # Add /usr/local/lib to the /etc/ld.so.conf. This was needed to get the loader to load the dependent libraries (e.g. xercesc) that are by default installed to /usr/local/lib to load. {noformat} echo /usr/local/lib >> /etc/ld.so.conf {noformat}\\ \\ h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a \\ jamstec_runmbarivis_displayalg \\ \\ This will display output, similar to the following. \*NOTE\* Windows display overlapped, not in the cascade pattern shown in this image. Just remember to click and drag them from on top of each other. \\ (click to enlarge)  !ScreenshotAlgorithmRunning.png|thumbnail!\\ \\ OR \\ jamstec_runmbarivis  \\ This will simply spew out the output from mbarivision into the console window.  \\ (click to enlarge)  !ScreenshotJamstecrunmbarivis.png|thumbnail!\\ \\ | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect \\ jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139Z.mov \\ {tip:title=Handy Hint}This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]\\ date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number. \\ E.g. 20080604T063139Z assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} | Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. | cd /home/aved/Video/20080604T063139Z.mov; jamstec_runprocess 20080604T063139Z.mov \\ | h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. *This must be executed in the root directory of the ppm frames*, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. *This must be executed in the root directory of the ppm frames*, Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 11240190 11829284 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796517 10388750 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-num=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-non-interesting-events \\ | \[yes\] \\ | If saving events, save non interesting events in addition to interesting event. Default is to not save non interesting events. \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average. \\ | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image. *Important* this only masks the area to look for detections - it does not mask the area from the saliency computation. \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | | \--mbari-saliency-dist= \\ | \[5\] \\ | The number of frames to delay between saliency map computations. Reduce this to improve your detection rate. Warning reducing this *will* increase your computation time. \\ |]]> 10356024 11829290 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}.If you want the mbarivision to be accessible by all users, example environment settings have been provided to add to your system. For example, on Fedora Linux, add these to /etc/profile.d. You must do this step to setup a machine that will run mbarivision as a Condor node. {noformat} cd cp aved.*sh /etc/profile.d/ {noformat} {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} h3. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 11796523 10388749 10356023 11829287 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796520 11272936 11240194 11829288 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796521 11272924 cp make install mpeg_encode /usr/local/bin {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision and AVED scripts|AVED Installation - Step 6. Build and Install mbarivision or pmbarivision and AVED scripts]. \\ \\ \\ \\ \\ \\ \\]]> 11240182 11272923 11240181 11829275 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}.If you want the mbarivision to be accessible by all users, example environment settings have been provided to add to your system. For example, on Fedora Linux, add these to /etc/profile.d. You must do this step to setup a machine that will run mbarivision as a Condor node. {noformat} cd cp aved.*sh /etc/profile.d/ {noformat} {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h3. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 11796508 11272926 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}.If you want the mbarivision to be accessible by all users, example environment settings have been provided to add to your system. For example, on Fedora Linux, add these to /etc/profile.d. It is recommended to do this step if you are setting up a machine that will run mbarivision as a Condor node. {noformat} cd cp aved.*sh /etc/profile.d/ {noformat} {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h3. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 11240184 11829278 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796511 11272925 11240183 11829277 this] to a USB thumbdrive. h3. Step 10.  Install network driver from thumbdrive {noformat} mount /media/usbdisk cd /media/usbdisk install -D -m 6644 e1000.ko /lib/modules/2.6.9-1.667smp/kernel/drivers/net/e1000/e1000.ko /sbin/depmod {noformat} h3. Step 11. Run kudzu to install net driver and setup the network with a static address {noformat}   kudzu {noformat}\\ e.g. for node 2, the settings should look something like:    /etc/sysconfig/networking/devices/ifcfg-eth0: DEVICE = eth0  ONBOOT = yes BOOTPROTO = static IPADDR = 192.168.1.2 NETMASK = 255.255.255.0 GATEWAY = 192.168.1.254 HWADDR = h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796510 11272928 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}.If you want the mbarivision to be accessible by all users, example environment settings have been provided to add to your system. For example, on Fedora Linux, add these to /etc/profile.d. It is recommended to do this step if you are setting up a machine that will run mbarivision as a Condor node. {noformat} cd cp aved.*sh /etc/profile.d/ {noformat} {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h3. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 11240186 11829279 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796512 11272930 11240188 11829282 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796515 11272929 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}.If you want the mbarivision to be accessible by all users, example environment settings have been provided to add to your system. For example, on Fedora Linux, add these to /etc/profile.d. You must do this step to setup a machine that will run mbarivision as a Condor node. {noformat} cd cp aved.*sh /etc/profile.d/ {noformat} {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h3. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 11240187 11829281 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796514 11272916 11240174 11829268 h3. Step 6. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 7. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 8. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796501 11272915 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P /usr/local gmake {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} Install the XML::Xerces library {noformat} export XERCESCROOT= export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} {tip:title=Handy Hint} If you installed the Xerces C+\+ library to a non-standard library location, be sure to add to the loader path in /etc/ld.so.conf the location, and run ldconfig -v to refresh the loader. {tip} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED Installation - Step 3. Build and Install Transcode and mpeg4ip Software].]]> 11240173 11829267 h3. Step 6. Change the hostname, e.g. for node 2 {noformat} hostname node8.private.net {noformat} h3. Step 7. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 8. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat} ]]> 11796500 11272918 cp make install mpeg_encode /usr/local/bin {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision and AVED scripts|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts]. \\ \\ \\ \\ \\ \\ \\]]> 11240176 11829270 h3. Step 6. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 7. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 8. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796503 11272917 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is diminishing, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue to the next optional step [AVED Installation - Step 5. Build and install Berkeley MPEG Encoder|AVED:AVED Installation - Step 5. Build and install Berkeley MPEG Encoder (optional)]\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 11240175 11829269 h3. Step 6. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 7. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 8. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796502 11272920 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}.If you want the mbarivision to be accessible by all users, example environment settings have been provided to add to your system. For example, on Fedora Linux, add these to /etc/profile.d. It is recommended to do this step if you are setting up a machine that will run mbarivision as a Condor node. {noformat} cd cp aved.*sh /etc/profile.d/ {noformat} {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h3. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 11240178 11829272 this] to a USB thumbdrive. h3. Step 10.  Install network driver from thumbdrive {noformat} mount /media/usbdisk cd /media/usbdisk install -D -m 6644 e1000.ko /lib/modules/2.6.9-1.667smp/kernel/drivers/net/e1000/e1000.ko /sbin/depmod {noformat} h3. Step 5. Run kudzu to install net driver and setup the network with a static address {noformat}   kudzu {noformat}\\ \\ e.g. for node 2, the settings should look something like:   /etc/sysconfig/networking/devices/ifcfg-eth0: DEVICE = eth0 ONBOOT = yes BOOTPROTO = static IPADDR = 192.168.1.2 NETMASK = 255.255.255.0 GATEWAY = 192.168.1.254 HWADDR = h3. Step 6. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 7. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 8. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796505 11272919 11240177 11272922 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is diminishing, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat} When you are done, you can skip to [step 6|AVED Installation - Step 6. Build and Install mbarivision or pmbarivision and AVED scripts], or continue to the next optional step [AVED Installation - Step 5. Build and install Berkeley MPEG Encoder|AVED:AVED Installation - Step 5. Build and install Berkeley MPEG Encoder (optional)]\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 11240180 11829274 this] to a USB thumbdrive. h3. Step 10.  Install network driver from thumbdrive {noformat} mount /media/usbdisk cd /media/usbdisk install -D -m 6644 e1000.ko /lib/modules/2.6.9-1.667smp/kernel/drivers/net/e1000/e1000.ko /sbin/depmod {noformat} h3. Step 11. Run kudzu to install net driver and setup the network with a static address {noformat}   kudzu {noformat} e.g. for node 2, the settings should look something like:    /etc/sysconfig/networking/devices/ifcfg-eth0: DEVICE = eth0  ONBOOT = yes BOOTPROTO = static IPADDR = 192.168.1.2 NETMASK = 255.255.255.0 GATEWAY = 192.168.1.254 HWADDR = h3.    h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796507 11272921 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P /usr/local gmake {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} Install the XML::Xerces library {noformat} export XERCESCROOT= export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} {tip:title=Handy Hint} If you installed the Xerces C+\+ library to a non-standard library location, be sure to add to the loader path in /etc/ld.so.conf the location, and run ldconfig -v to refresh the loader. {tip} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED Installation - Step 6. Build and Install mbarivision or pmbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED Installation - Step 3. Build and Install Transcode and mpeg4ip Software].]]> 11240179 11829260 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P /usr/local gmake {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} Install the XML::Xerces library {noformat} export XERCESCROOT= export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} {tip:title=Handy Hint} If you installed the Xerces C+\+ library to a non-standard library location, be sure to add to the loader path in /etc/ld.so.conf the location, and run ldconfig -v to refresh the loader. {tip} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED Installation - Step 6. Build and Install (p)mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED Installation - Step 3. Build and Install Transcode and mpeg4ip Software].]]> 11796493 11829261 export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} {tip:title=Handy Hint} If you installed the Xerces C+\+ library to a non-standard library location, be sure to add to the loader path in /etc/ld.so.conf the location, and run ldconfig -v to refresh the loader. {tip} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED Installation - Step 6. Build and Install (p)mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED Installation - Step 3. Build and Install Transcode and mpeg4ip Software].]]> 11796494 11272910 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}.If you want the mbarivision to be accessible by all users, example environment settings have been provided to add to your system. For example, on Fedora Linux, add these to /etc/profile.d. It is recommended to do this step if you are setting up a machine that will run mbarivision as a Condor node. {noformat} cd cp aved.*sh /etc/profile.d/ {noformat} {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h3. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 11240168 11272913 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}.If you want the mbarivision to be accessible by all users, example environment settings have been provided to add to your system. For example, on Fedora Linux, add these to /etc/profile.d. It is recommended to do this step if you are setting up a machine that will run mbarivision as a Condor node. {noformat} cd cp aved.*sh /etc/profile.d/ {noformat} {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h3. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 11240171 11829254 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now, go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 11796486 6226307 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local}} by default; of course you can change that with the usual {{\--prefix}} argument to {{configure}}. {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h2. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 6259089 11829256 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now, go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 11796488 11829258 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  Once you get the password to the iLab repository, check-out the saliency code from the date 2008-04-15 using svn. *Important* - we unfortunately are working with an older version of the toolkit because we haven't had time to port our code to work with the latest saliency revision. So, to be compatible with the version we are working with, you must checkout the release on the date 2008-04-15. The checkout command: {noformat} svn checkout --username anonsvn svn://iLab.usc.edu/trunk/saliency --revision {2008-04-15} saliency {noformat} When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now, go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 11796490 11272893 11240149 11272891 11240147 11272890 11240146 11272888 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed to use. Passwords for both the root and aved users have been sent to Dhugal. Two additional steps were required for this installation: # Add manual links for the dc1394 control libraries. This was needed to get saliency to compile. {noformat} cd /usr/lib ln -s libdc1394.so.22 libdc1394_control.so ln -s libdc1394.so.22 libdc1394.so {noformat} # Add /usr/local/lib to the /etc/ld.so.conf. This was needed to get the loader to load the dependent libraries (e.g. xercesc) that are by default installed to /usr/local/lib to load. {noformat} echo /usr/local/lib >> /etc/ld.so.conf {noformat}\\ \\ h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a \\ jamstec_runmbarivis_displayalg \\ \\ This will display output, similar to the following. \*NOTE\* Windows display overlapped, not in the cascade pattern shown in this image. Just remember to click and drag them from on top of each other. \\ (click to enlarge)  !ScreenshotAlgorithmRunning.png|thumbnail!\\ \\ OR \\ jamstec_runmbarivis  \\ This will simply spew out the output from mbarivision into the console window.  \\ (click to enlarge)  !ScreenshotJamstecrunmbarivis.png|thumbnail!\\ \\ | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect \\ jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139Z.mov \\ {tip:title=Handy Hint}This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]\\ date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number. \\ E.g. 20080604T063139Z assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} | Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. | cd /home/aved/Video/20080604T063139Z.mov; jamstec_runprocess 20080604T063139Z.mov \\ | h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. *This must be executed in the root directory of the ppm frames*, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. *This must be executed in the root directory of the ppm frames*, Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 11240144 11829368 11796609 11272887 11240143 11272886 11240142 11829366 11796607 11829364 11796605 11829361 11796602 11829362 11796603 11829359 11796598 11829357 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is diminishing, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat} When you are done, you can skip to [step 6|mbarivision Installation - Step 6. Build and Install mbarivision], or continue to the next optional step [AVED Installation - Step 5. Build and install Berkeley MPEG Encoder|mbarivision Installation - Step 5. Build and install Berkeley MPEG Encoder (optional)]\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 11796595 11829355 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 11796593 11829356 11796594 11829353 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 11796591 11829354 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 11796592 11829351 export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} {tip:title=Handy Hint} If you installed the Xerces C+\+ library to a non-standard library location, be sure to add to the loader path in /etc/ld.so.conf the location, and run ldconfig -v to refresh the loader. {tip} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED Installation - Step 6. Build and Install (p)mbarivision], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|mbarivision Installation - Step 3. Build and Install Transcode and mpeg4ip Software].]]> 11796589 11829352 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is diminishing, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat} When you are done, you can skip to [step 6|AVED Installation - Step 6. Build and Install (p)mbarivision], or continue to the next optional step [AVED Installation - Step 5. Build and install Berkeley MPEG Encoder|mbarivision Installation - Step 5. Build and install Berkeley MPEG Encoder (optional)]\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 11796590 11829349 cp make install mpeg_encode /usr/local/bin {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision and AVED scripts|AVED Installation - Step 6. Build and Install (p)mbarivision]. \\ \\ \\ \\ \\ \\ \\]]> 11796587 11829350 11796588 11829347 export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} {tip:title=Handy Hint} If you installed the Xerces C+\+ library to a non-standard library location, be sure to add to the loader path in /etc/ld.so.conf the location, and run ldconfig -v to refresh the loader. {tip} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED Installation - Step 6. Build and Install (p)mbarivision], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED Installation - Step 3. Build and Install Transcode and mpeg4ip Software].]]> 11796585 11829348 11796586 11829344 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is diminishing, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat} When you are done, you can skip to [step 6|AVED Installation - Step 6. Build and Install (p)mbarivision], or continue to the next optional step [AVED Installation - Step 5. Build and install Berkeley MPEG Encoder|AVED:AVED Installation - Step 5. Build and install Berkeley MPEG Encoder (optional)]\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 11796582 11829343 export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} {tip:title=Handy Hint} If you installed the Xerces C+\+ library to a non-standard library location, be sure to add to the loader path in /etc/ld.so.conf the location, and run ldconfig -v to refresh the loader. {tip} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED Installation - Step 6. Build and Install (p)mbarivision], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED Installation - Step 3. Build and Install Transcode and mpeg4ip Software].]]> 11796581 11829346 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is diminishing, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat} When you are done, you can skip to [step 6|AVED Installation - Step 6. Build and Install (p)mbarivision], or continue to the next optional step [AVED Installation - Step 5. Build and install Berkeley MPEG Encoder|mbarivision Installation - Step 5. Build and install Berkeley MPEG Encoder (optional)]\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 11796584 11829345 cp make install mpeg_encode /usr/local/bin {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision and AVED scripts|AVED Installation - Step 6. Build and Install (p)mbarivision]. \\ \\ \\ \\ \\ \\ \\]]> 11796583 11829340 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now, go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 11796578 11829339 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 11796577 11829342 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 11796580 11829341 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now, go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 11796579 11829336 11796574 11829335 11796573 6979599 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average. \\ | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | | \--mbari-saliency-dist= \\ | \[5\] \\ | The number of frames to delay between saliency map computations. Reduce this to improve your detection rate. Warning reducing this *will* increase your computation time. \\ |]]> 6946831 11829337 11796575 11829331 11796568 9404929 9372188 11829333 11796570 6979597 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average.\\ | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | | \--mbari-saliency-dist= \\ | \[5\] \\ | The number of frames to delay between saliency map computations. Reduce this to improve your detection rate. Warning - this will increase your computation time. \\ |]]> 6946829 8388880 8356123 8388882 8356126 8388877 8356120 11272805 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 11240058 11272804 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 11240057 11272803 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 11240056 6226214 cd $XERCESCROOT/src/xerces runConfigure -p linux gmake sudo gmake install {noformat} {color:#990000}TODO: Verify this - is this for mbarivision ? make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib){color} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat}]]> 6258993 11272809 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 11240062 11272808 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 11240061 11272807 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 11240060 11272798 11240051 11272802 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 11240055 6226296 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h2. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have compiled over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 6259078 11829498 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796741 6226295 cd $XERCESCROOT/src/xerces runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} {color:#990000}TODO: Verify this - is this for mbarivision ? make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib){color} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat}]]> 6259077 6226298 cd $XERCESCROOT/src/xerces runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat}]]> 6259080 6226292 cd $XERCESCROOT/src/xerces runConfigure -p linux gmake sudo gmake install {noformat} {color:#990000}TODO: Verify this - is this for mbarivision ? make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib){color} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat}]]> 6259074 6226294 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h2. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have compiled over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 6259076 11829506 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/ {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/mpd.conf {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc {noformat} h2. SSH configuration Add to /etc/ssh/ssh_config, then restart the service Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.51 /usr/lib/ cpush /usr/lib/libavcodec.so.52 /usr/lib/ cpush /usr/lib/libavcodec.so.52 /usr/lib/ cpush /usr/lib/libavcodec.so.51.40.4 /usr/lib/ cpush /usr/lib/libavformat.so.51.12.1 /usr/lib cpush /usr/lib/libavformat.so.51 /usr/lib cpush /usr/lib/libavformat.so.51.12.1 /usr/lib cpush /usr/lib/libavformat.so.51.12.1 /usr/lib/ cpush /usr/lib/libavformat.so.51.12.1 cpush /usr/lib/libavutil.so.*.* /usr/lib/ cpush /usr/lib/libavutil.so.* /usr/lib cpush /usr/lib/libavutil.so /usr/lib cexec 'ldconfig' {noformat}]]> 11796749 11829503 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/ {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/ {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc {noformat} h2. SSH configuration Add to /etc/ssh/ssh_config, then restart the service Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.51 /usr/lib/ cpush /usr/lib/libavcodec.so.52 /usr/lib/ cpush /usr/lib/libavcodec.so.52 /usr/lib/ cpush /usr/lib/libavcodec.so.51.40.4 /usr/lib/ cpush /usr/lib/libavformat.so.51.12.1 /usr/lib cpush /usr/lib/libavformat.so.51 /usr/lib cpush /usr/lib/libavformat.so.51.12.1 /usr/lib cpush /usr/lib/libavformat.so.51.12.1 /usr/lib/ cpush /usr/lib/libavformat.so.51.12.1 cpush /usr/lib/libavutil.so.*.* /usr/lib/ cpush /usr/lib/libavutil.so.* /usr/lib cpush /usr/lib/libavutil.so /usr/lib cexec 'ldconfig' {noformat}]]> 11796746 11829504 > /etc/mpd.conf {noformat} # Push it to the the other nodes {noformat} cpush /etc/mpd.conf {noformat} h2. User profile setup Install aved.sh/csh similar to following in the /etc/profile.d/ {noformat} export MPDIR=/opt/mpich2-1.1.1p1 export PATH=$MPDIR/bin:$PATH:/usr/local/bin if [ -d /home/aved/bin ]; then export PATH=$PATH:/home/aved/bin; fi if [ -d /home/aved/scripts ]; then export PATH=$PATH:/home/aved/scripts; fi if [ -d /mnt/scratch ]; then export SCRATCH_DIR=/mnt/scratch; fi {noformat} When done push these to the other nodes: {noformat} cpush /etc/profile.d/aved.* /etc/profile.d/ {noformat} h2. Install mpd similar to the following in etc/rc.d/init.d/ {noformat} !/bin/sh # # Start or stop system wide mpd daemon # Source the aved functions . /etc/profile.d/aved.sh case "$1" in start) # This assumes only nodes and not the master are listed in the mpd.hosts file # because the master is not typically listed as a worker node c=`wc -l $MPDIR/etc/mpd.hosts | awk '{print $1}'` # Add one to include the master ((c += 1)) if [ ! -e '/tmp/mpd2.console_root' ]; then mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" else echo "restarting mpd" mpdallexit mpdboot --ncpus=2 --totalnum=$c --file="$MPDIR/etc/mpd.hosts --mpd=$MPDIR/bin/mpd.py" fi mpdtrace ;; stop) if [ -e '/tmp/mpd2.console_root' ]; then mpdallexit #remove tmp file in case mpdallexit cmd fails if [ -e '/tmp/mpd2.console_root' ]; then rm /tmp/mpd2.console_root fi echo "mpd daemon stopped" else echo "mpd daemon already stopped" fi ;; status) if [ -e '/tmp/mpd2.console_root' ]; then mpdtrace -l else echo "mpd daemon not running" fi ;; *) echo "usage: $0 {start|stop|status}" ;; "/etc/rc.d/init.d/mpd" 53L, 1411C {noformat} {noformat} cpush /etc/rc.d/init.d/mpd /etc {noformat} h2. SSH configuration Add to /etc/ssh/ssh_config, then restart the service Host * ForwardX11 yes StrictHostKeyChecking no UsePrivilegedPort no h2. Copy FFMPEG library dependencies to all nodes These dependencies are required in the pmbarivision code. Push dependencies to the client nodes and refresh the dynamic linker: {noformat} cpush /usr/lib/libavcodec.so.51 /usr/lib/ cpush /usr/lib/libavcodec.so.52 /usr/lib/ cpush /usr/lib/libavcodec.so.52 /usr/lib/ cpush /usr/lib/libavcodec.so.51.40.4 /usr/lib/ cpush /usr/lib/libavformat.so.51.12.1 /usr/lib cpush /usr/lib/libavformat.so.51 /usr/lib cpush /usr/lib/libavformat.so.51.12.1 /usr/lib cpush /usr/lib/libavformat.so.51.12.1 /usr/lib/ cpush /usr/lib/libavformat.so.51.12.1 cpush /usr/lib/libavutil.so.*.* /usr/lib/ cpush /usr/lib/libavutil.so.* /usr/lib cpush /usr/lib/libavutil.so /usr/lib cexec 'ldconfig' {noformat}]]> 11796747 6226305 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h2. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 6259087 11829502 11796745 11829499 11796742 11829482 11796725 6226281 6259063 11829479 11796722 11829478 11796721 11829477 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796720 11829476 11796719 6226277 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexbility in the video containers and since support for OpenQuicktime is waning abandoning it was logical. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. Check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following:\\ {noformat} cd ./configure make sudo make install {noformat}\\ \\ \\ \\ \\ \\ \\]]> 6259059 11829475 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796718 6226278 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is waning, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat}\\ \\ \\ \\ \\ \\ \\ \\]]> 6259060 6226288 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is waning, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 6259070 6226290 6259072 6226283 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is waning, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\]]> 6259065 11829485 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. *It is important to format the filenames with a single dot '.' e.g. a filename formatted like T.f00000.ppm isn't supported, but Tf00000.ppm is okay, in this case you would pass the in argument with Tf#.ppm.*| | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-num=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-non-interesting-events \\ | \[yes\] \\ | If saving events, save non interesting events in addition to interesting event. Default is to not save non interesting events. \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \-mbari-mosaic-benthic-stills | \[no\] | Implements good choice of options to experiment with processing still images from a still or moving camera traversing the sea bottom. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --mbari-cache-size=2 --mbari-max-WTA-points=15 --mbari-max-evolve-msec=15000 --vc-type=OIC --use-random=false --test-mode=true --oricomp-type=Steerable --mbari-cache-size=2 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-benthic-video | \[no\] | Implements good choice of options to experiment with processing video from a moving camera traversing the sea bottom. EQUIVALENT TO: --mbari-saliency-dist=5 --mbari-tracking-mode=NearestNeighbor --mbari-saliency-input-image=DiffMean --mbari-segment-algorithm-input-image=MaxRGB --vc-type=O:5IC --use-random=false --test-mode=true --ori-interaction=None --oricomp-type=Steerable --mbari-cache-size=15 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-midwater-video | \[no\] | Implements good choice of options to experiment with processing video from a moving camera traversing the midwater sea column. EQUIVALENT TO: --mbari-saliency-dist=5 --mbari-tracking-mode=KalmanFilter --mbari-saliency-input-image=DiffMean --mbari-segment-algorithm-input-image=MaxRGB --vc-type=O:5IC --use-random=false --test-mode=true --mbari-cache-size=10 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-mosaic-stills | \[no\] | Implements good choice of options to experiment with still frames collected from a moving camera in mosaic form. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --boring-sm-mv=0.25 --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --vc-type=Variance --use-random=false --mbari-saliency-input-image=Raw --mbari-cache-size=2 --mbari-max-WTA-points=25 --mbari-max-evolve-msec=15000 \\ | | \-mbari-timelapse-stills | \[no\] | Implements good choice of options to experiment with still frames collected from a stationary time-lapse camera. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=NearestNeighbor --mbari-keep-boring-WTA-points=yes --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --mbari-cache-size=10 --qtime-decay=1.0 --vc-type=Variance --use-random=false --mbari-max-WTA-points=30 --mbari-max-evolve-msec=15000 --use-random=false --use-older-version=false \\ | | \-mbari-timelapse-rover-stills | \[no\] | Implements good choice of options to experiment with time-lapse still frames collected from a benthic moving camera . EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --qtime-decay=1.0 --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --vc-type=O:5IC --use-random=false --mbari-max-WTA-points=15 --mbari-max-evolve-msec=15000 \\ | | \--mbari-max-WTA-points= | \[20\] | Maximum number of winner-take-all points to find in each frame \\ | | \--mbari-max-evolve-msec= | \[500\] | Maximum amount of time in milliseconds to evolve the brain until stopping \\ | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average. \\ | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Tracking mode used to track events between frames \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-segment-algorithm-input-image= | \[MaxRGB\] \\ | Segment algorithm input images type \\ | | \--mbari-segment-algorithm-se-type= | \[benthic\] \\ | Jerome Mariette's segmentation algorithm structure element test \\ | | \--mbari-segment-input-image= | \[DiffMean\] \\ | Saliency input image type \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image. *Important* this only masks the area to look for detections - it does not mask the area from the saliency computation. \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | | \--mbari-saliency-dist= \\ | \[5\] \\ | The number of frames to delay between saliency map computations Reduce this to improve your detection rate. Warning reducing this *will* increase your computation time. \\ |]]> 11796728 11829484 11796727 6226285 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is waning, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 6259067 11829483 11796726 6226286 6259068 11829471 11796714 11829473 11796716 11829474 h3. Step 12. Change the hostname, e.g. for node 2 {noformat} hostname node2.private.net {noformat} h3. Step 13. Modify the fstab file to include mounts in the fstab file on the thumbdrive h3. Step 14. Replace the sshd_config with the file on the thumbdrive {noformat} cp -f /mount/usbdisk/sshd_config /etc/ssh {noformat}]]> 11796717 5406880 ) ** [Xerces-C |http://xerces.apache.org/xerces-c/] (version ) ** XML::Simple perl module(latest version) ** [Transcode|http://www.transcoding.org/cgi-bin/transcode] (optional version 1.0.2 or >) * *Download and uncompress* the AVED source files that are distributed as tar'ed files, then build the source. h1. Preparation for building the Saliency Toolkit Most importantly, the AVED software requires the Saliency Toolkit from the [ilab|http://ilab.usc.edu/bu/] at Caltech. The Saliency toolkit is distributed as source files, so you must compile them before to compile AVED. To get this software, you must ask for permission to use it by following the instructions on the bottom of this page: [http://ilab.usc.edu/toolkit/downloads.shtml]. Let them know you will be using this with the AVED software from MBARI.   As long are you use the Toolkit for non-commercial use, you should be granted access to the code. You will be given a user login and password to check out the code from the ilab SVN repository. If you don't have [Subversion|http://subversion.tigris.org/] installed, you can install it using: {noformat} yum install subversion {noformat} Once, you get a username and password, you can check-out the code using svn: {noformat} svn checkout --username anonsvn svn://iLab.usc.edu/trunk/saliency {noformat} || Library || RPM Packages || Fedora command \\ || | libX11 | xorg-x11-proto-devel \\ | yum \-y install xorg-x11-proto-devel | | gcc \\ | gcc-c+\+ | yum \-y install gcc-c+\+ \\ | | tclsh \\ | tclx \\ | yum \-y install tclx \\ | | libXShm \\ | libXext-devel \\ | yum \-y install libXext-devel | | libbz2 | bzip2-devel \\ | yum \-y install bzip2-devel \\ | | libz \\ | zlib-devel | yum \-y install zlib-devel | | lpng \\ | libpng and libpng-devel \\ | yum \-y install libpng; yum \-y install libpng-devel \\ | | ljpeg \\ | libjpeg and libjpeg-devel \\ | yum \-y install libjpeg; yum \-y install libjpeg-devel | | libavcodec, libavutil, libavformat \\ | ffmpeg and ffmpeg-devel or install from sources \\ | | To install ffmpeg from sources, get the last version (you need subversion to check the code out, if not yum install subversion):              {noformat} svn checkout svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg cd ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the transcode software Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required to make AVED working, if you provid AVED direcly frames, you can go to the next step. Transcode can be install from a RPM using the yum command, but it is not the basic depot boxes, it can be found on the livna depot that you can download at: [http://rpm.livna.org/rlowiki/]. Download it and install the rpm. Or you can get the code from [http://www.transcoding.org/cgi-bin/transcode]and install it. \\ {noformat} rpm -ivh livna-release-xxxxx.rpm yum install transcode {noformat} If you need to install it from source (rpm transcode are not available for all distributions), first begin by downloading the source from: [http://www.transcoding.org/cgi-bin/transcode], then uncompress the source (bunzip2 is required, if you don't have it: yum install bunzip2). {noformat} bunzip2 transcode-xxxxxx.tar.bz2 tar xvf transcode-xxxxxxx.tar {noformat} Transcode uses shared libraries, here is the list and the RPM packages that provides them:     || Library || RPM Packages || Fedora command \\ || | mpeg2dec | mpeg2dec and mpeg2dec-devel \\ | yum install mpeg2dec; yum install mpeg2dec-devel \\ | | libXv \\ | libXv-devel | yum install libXv-devel \\ |  Then go in the transcode directory: \\ {noformat} cd transcode-xxxxxxx ./configure --disable-lame --disable-libdvdread make sudo make install {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. * Now change to the new directory cd mbarivision * Run configure. You can start with the defaults. If you need to modify the installation parameters you can read the next section. ./configure * Build the code make Install the code * make install \\]]> 5374130 5406882 ) ** [Xerces-C |http://xerces.apache.org/xerces-c/] (version ) ** XML::Simple perl module(latest version) ** [Transcode|http://www.transcoding.org/cgi-bin/transcode] (optional version 1.0.2 or >) * *Download and uncompress* the AVED source files that are distributed as tar'ed files, then build the source. h1. Preparation for building the Saliency Toolkit Most importantly, the AVED software requires the Saliency Toolkit from the [ilab|http://ilab.usc.edu/bu/] at Caltech. The Saliency toolkit is distributed as source files, so you must compile them before to compile AVED. To get this software, you must ask for permission to use it by following the instructions on the bottom of this page: [http://ilab.usc.edu/toolkit/downloads.shtml]. Let them know you will be using this with the AVED software from MBARI.   As long are you use the Toolkit for non-commercial use, you should be granted access to the code. You will be given a user login and password to check out the code from the ilab SVN repository. If you don't have [Subversion|http://subversion.tigris.org/] installed, you can install it using: {noformat} yum install subversion {noformat} Once, you get a username and password, you can check-out the code using svn: {noformat} svn checkout --username anonsvn svn://iLab.usc.edu/trunk/saliency {noformat} || Library || RPM Packages || Fedora command \\ || | libX11 | xorg-x11-proto-devel \\ | yum \-y install xorg-x11-proto-devel | | gcc \\ | gcc-c+\+ | yum \-y install gcc-c+\+ \\ | | tclsh \\ | tclx \\ | yum \-y install tclx \\ | | libXShm \\ | libXext-devel \\ | yum \-y install libXext-devel | | libbz2 | bzip2-devel \\ | yum \-y install bzip2-devel \\ | | libz \\ | zlib-devel | yum \-y install zlib-devel | | lpng \\ | libpng and libpng-devel \\ | yum \-y install libpng; yum \-y install libpng-devel \\ | | ljpeg \\ | libjpeg and libjpeg-devel \\ | yum \-y install libjpeg; yum \-y install libjpeg-devel | | libavcodec, libavutil, libavformat \\ | ffmpeg and ffmpeg-devel or install from sources \\ | | To install ffmpeg from sources, get the last version (you need subversion to check the code out, if not yum install subversion):              {noformat} svn checkout svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg cd ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the minimal build required for running the AVED software requires that you make _core_ and _tprogs_ with: it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3. Building the Transcode software (optional) Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required for AVED to work if your video is already broken into individual frames. If your video is on a container like an avi, mov, or asf, you might want this tool to convert your video into individual frames for processing. If not, skip this step. Transcode can be install from a RPM using the yum command, but it first must be downloaded from: [http://rpm.livna.org/rlowiki/]. Download it and install the rpm. Or, you can get the source code from [http://www.transcoding.org/cgi-bin/transcode]and install it. \\ {noformat} rpm -ivh livna-release-xxxxx.rpm yum install transcode {noformat} If you need to install it from source (rpm transcode are not available for all distributions), first begin by downloading the source from: [http://www.transcoding.org/cgi-bin/transcode], then uncompress the source. {noformat} bunzip2 transcode-xxxxxx.tar.bz2 tar xvf transcode-xxxxxxx.tar {noformat} Transcode uses shared libraries, here is the list and the RPM packages that provides them:     || Library || RPM Packages || Fedora command \\ || | mpeg2dec | mpeg2dec and mpeg2dec-devel \\ | yum install mpeg2dec; yum install mpeg2dec-devel \\ | | libXv \\ | libXv-devel | yum install libXv-devel \\ |  Then go in the transcode directory and build it: \\ {noformat} cd transcode-xxxxxxx ./configure --disable-lame --disable-libdvdread make sudo make install {noformat}\\ h3. Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. * Now change to the new directory cd mbarivision * Run configure. You can start with the defaults. If you need to modify the installation parameters you can read the next section. ./configure * Build the code make Install the code * make install \\]]> 5374132 5406876 ) ** [Xerces-C |http://xerces.apache.org/xerces-c/] (version ) ** XML::Simple perl module(latest version) ** [Transcode|http://www.transcoding.org/cgi-bin/transcode] (optional version 1.0.2 or >) * *Download and uncompress* the AVED source files that are distributed as tar'ed files, then build the source. h1. Preparation for install  Most importantly, the AVED software requires the Saliency Toolkit from the folks at Caltech. The Saliency toolkit is distributed as source files, so you must compile them before to compile AVED. To get this software, you must ask for permission to use it by following the instructions on the bottom of this page: [http://ilab.usc.edu/toolkit/downloads.shtml]. Let them know you will be using this with the AVED software from MBARI.   As long are you are using the Toolkit for non-commercial use, you should be granted access to the code. You will be given a user login and password to check out the code from the ilab SVN repository. If you don't have SVN installed, you can install it using: {noformat} yum install subversion {noformat} h5. Preparation for installing the Saliency Toolkit The Saliency Toolkit C+\+ source code requires the latest version of g+\+ (3.x) and other non-standard packages installed on your Linux distribution.  Here is the list and the RPM packages that provides the needed dependencies for Saliency, based on our latest experience with Fedora Core 9: || Library || RPM Packages || Fedora command \\ || | libX11 | xorg-x11-proto-devel \\ | yum \-y install xorg-x11-proto-devel | | gcc \\ | gcc-c+\+ | yum \-y install gcc-c+\+ \\ | | tclsh \\ | tclx \\ | yum \-y install tclx \\ | | libXShm \\ | libXext-devel \\ | yum \-y install libXext-devel | | libbz2 | bzip2-devel \\ | yum \-y install bzip2-devel \\ | | libz \\ | zlib-devel | yum \-y install zlib-devel | | lpng \\ | libpng and libpng-devel \\ | yum \-y install libpng; yum \-y install libpng-devel \\ | | ljpeg \\ | libjpeg and libjpeg-devel \\ | yum \-y install libjpeg; yum \-y install libjpeg-devel | | libavcodec, libavutil, libavformat \\ | ffmpeg and ffmpeg-devel or install from sources \\ | | To install ffmpeg from sources, get the last version (you need subversion to check the code out, if not yum install subversion):              {noformat} svn checkout svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg cd ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the transcode software Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required to make AVED working, if you provid AVED direcly frames, you can go to the next step. Transcode can be install from a RPM using the yum command, but it is not the basic depot boxes, it can be found on the livna depot that you can download at: [http://rpm.livna.org/rlowiki/]. Download it and install the rpm. Or you can get the code from [http://www.transcoding.org/cgi-bin/transcode]and install it. \\ {noformat} rpm -ivh livna-release-xxxxx.rpm yum install transcode {noformat} If you need to install it from source (rpm transcode are not available for all distributions), first begin by downloading the source from: [http://www.transcoding.org/cgi-bin/transcode], then uncompress the source (bunzip2 is required, if you don't have it: yum install bunzip2). {noformat} bunzip2 transcode-xxxxxx.tar.bz2 tar xvf transcode-xxxxxxx.tar {noformat} Transcode uses shared libraries, here is the list and the RPM packages that provides them:     || Library || RPM Packages || Fedora command \\ || | mpeg2dec | mpeg2dec and mpeg2dec-devel \\ | yum install mpeg2dec; yum install mpeg2dec-devel \\ | | libXv \\ | libXv-devel | yum install libXv-devel \\ |  Then go in the transcode directory: \\ {noformat} cd transcode-xxxxxxx ./configure --disable-lame --disable-libdvdread make sudo make install {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. * Now change to the new directory cd mbarivision * Run configure. You can start with the defaults. If you need to modify the installation parameters you can read the next section. ./configure * Build the code make Install the code * make install \\]]> 5374126 5406878 ) ** [Xerces-C |http://xerces.apache.org/xerces-c/] (version ) ** XML::Simple perl module(latest version) ** [Transcode|http://www.transcoding.org/cgi-bin/transcode] (optional version 1.0.2 or >) * *Download and uncompress* the AVED source files that are distributed as tar'ed files, then build the source. h1. Preparation for installing the Saliency Toolkit Most importantly, the AVED software requires the Saliency Toolkit from the [ilab|http://ilab.usc.edu/bu/] at Caltech. The Saliency toolkit is distributed as source files, so you must compile them before to compile AVED. To get this software, you must ask for permission to use it by following the instructions on the bottom of this page: [http://ilab.usc.edu/toolkit/downloads.shtml]. Let them know you will be using this with the AVED software from MBARI.   As long are you use the Toolkit for non-commercial use, you should be granted access to the code. You will be given a user login and password to check out the code from the ilab SVN repository. If you don't have SVN installed, you can install it using: {noformat} yum install subversion {noformat} h2. Preparation for installing the Saliency Toolkit The Saliency Toolkit C+\+ source code requires the latest version of g+\+ (3.x) and other non-standard packages installed on your Linux distribution.  Here is the list and the RPM packages that provides the needed dependencies for Saliency, based on our latest experience with Fedora Core 9: || Library || RPM Packages || Fedora command \\ || | libX11 | xorg-x11-proto-devel \\ | yum \-y install xorg-x11-proto-devel | | gcc \\ | gcc-c+\+ | yum \-y install gcc-c+\+ \\ | | tclsh \\ | tclx \\ | yum \-y install tclx \\ | | libXShm \\ | libXext-devel \\ | yum \-y install libXext-devel | | libbz2 | bzip2-devel \\ | yum \-y install bzip2-devel \\ | | libz \\ | zlib-devel | yum \-y install zlib-devel | | lpng \\ | libpng and libpng-devel \\ | yum \-y install libpng; yum \-y install libpng-devel \\ | | ljpeg \\ | libjpeg and libjpeg-devel \\ | yum \-y install libjpeg; yum \-y install libjpeg-devel | | libavcodec, libavutil, libavformat \\ | ffmpeg and ffmpeg-devel or install from sources \\ | | To install ffmpeg from sources, get the last version (you need subversion to check the code out, if not yum install subversion):              {noformat} svn checkout svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg cd ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the transcode software Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required to make AVED working, if you provid AVED direcly frames, you can go to the next step. Transcode can be install from a RPM using the yum command, but it is not the basic depot boxes, it can be found on the livna depot that you can download at: [http://rpm.livna.org/rlowiki/]. Download it and install the rpm. Or you can get the code from [http://www.transcoding.org/cgi-bin/transcode]and install it. \\ {noformat} rpm -ivh livna-release-xxxxx.rpm yum install transcode {noformat} If you need to install it from source (rpm transcode are not available for all distributions), first begin by downloading the source from: [http://www.transcoding.org/cgi-bin/transcode], then uncompress the source (bunzip2 is required, if you don't have it: yum install bunzip2). {noformat} bunzip2 transcode-xxxxxx.tar.bz2 tar xvf transcode-xxxxxxx.tar {noformat} Transcode uses shared libraries, here is the list and the RPM packages that provides them:     || Library || RPM Packages || Fedora command \\ || | mpeg2dec | mpeg2dec and mpeg2dec-devel \\ | yum install mpeg2dec; yum install mpeg2dec-devel \\ | | libXv \\ | libXv-devel | yum install libXv-devel \\ |  Then go in the transcode directory: \\ {noformat} cd transcode-xxxxxxx ./configure --disable-lame --disable-libdvdread make sudo make install {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. * Now change to the new directory cd mbarivision * Run configure. You can start with the defaults. If you need to modify the installation parameters you can read the next section. ./configure * Build the code make Install the code * make install \\]]> 5374128 5406871 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the transcode software Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required to make AVED working, if you provid AVED direcly frames, you can go to the next step. Transcode can be install from a RPM using the yum command, but it is not the basic depot boxes, it can be found on the livna depot that you can download at: [http://rpm.livna.org/rlowiki/]. Download it and install the rpm. Or you can get the code from [http://www.transcoding.org/cgi-bin/transcode]and install it. \\ {noformat} rpm -ivh livna-release-xxxxx.rpm yum install transcode {noformat} If you need to install it from source (rpm transcode are not available for all distributions), first begin by downloading the source from: [http://www.transcoding.org/cgi-bin/transcode], then uncompress the source (bunzip2 is required, if you don't have it: yum install bunzip2). {noformat} bunzip2 transcode-xxxxxx.tar.bz2 tar xvf transcode-xxxxxxx.tar {noformat} Transcode uses shared libraries, here is the list and the RPM packages that provides them:     || Library || RPM Packages || Fedora command \\ || | mpeg2dec | mpeg2dec and mpeg2dec-devel \\ | yum install mpeg2dec; yum install mpeg2dec-devel \\ | | libXv \\ | libXv-devel | yum install libXv-devel \\ |  Then go in the transcode directory: \\ {noformat} cd transcode-xxxxxxx ./configure --disable-lame --disable-libdvdread make sudo make install {noformat}\\ \\ \\ \\ \\ \\ \\ \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. * Now change to the new directory cd mbarivision * Run configure. You can start with the defaults. If you need to modify the installation parameters you can read the next section. ./configure * Build the code make Install the code * make install \\]]> 5374121 5406874 ) ** [Xerces-C |http://xerces.apache.org/xerces-c/] (version ) ** XML::Simple perl module(latest version) ** [Transcode|http://www.transcoding.org/cgi-bin/transcode] (optional version 1.0.2 or >) * *Download and uncompress* the AVED source files that are distributed as tar'ed files, then build the source. h1. Preparation for install  Most importantly, the AVED software requires the Saliency Toolkit from the folks at Caltech. The Saliency toolkit is distributed as source files, so you must compile them before to compile AVED. To get this software, you must ask for permission to use it by following the instructions on the bottom of this page: [http://ilab.usc.edu/toolkit/downloads.shtml]. Let them know you will be using this with the AVED software from MBARI.   As long are you are using the Toolkit for non-commercial use, you should be granted access to the code. You will be given a user login and password to check out the code from the ilab SVN repository. If you don't have SVN installed, you can install it using: {noformat} yum install subversion {noformat} In addition to the Saliency Toolkit, there are a number of other shared libraries that AVED uses. Some of the libraries can be installed from RPM, and some must be installed from source. Additionally, some development RPM's are required which are normally called the same name as the package suffixed by \-devel or \-dev. These development packages contain the header files (xxx.h) that AVED needs to build with the shared libraries. If you build a library from sources you already have these header files.   h5. Preparation for installing the Saliency Toolkit The Saliency Toolkit C+\+ source code requires the latest version of g+\+ (3.x) and other non-standard packages installed on your Linux distribution.  Here is the list and the RPM packages that provides the needed dependencies for Saliency, based on our latest experience with Fedora Core 9: || Library || RPM Packages || Fedora command \\ || | libX11 | xorg-x11-proto-devel \\ | yum \-y install xorg-x11-proto-devel | | gcc \\ | gcc-c+\+ | yum \-y install gcc-c+\+ \\ | | tclsh \\ | tclx \\ | yum \-y install tclx \\ | | libXShm \\ | libXext-devel \\ | yum \-y install libXext-devel | | libbz2 | bzip2-devel \\ | yum \-y install bzip2-devel \\ | | libz \\ | zlib-devel | yum \-y install zlib-devel | | lpng \\ | libpng and libpng-devel \\ | yum \-y install libpng; yum \-y install libpng-devel \\ | | ljpeg \\ | libjpeg and libjpeg-devel \\ | yum \-y install libjpeg; yum \-y install libjpeg-devel | | libavcodec, libavutil, libavformat \\ | ffmpeg and ffmpeg-devel or install from sources \\ | | To install ffmpeg from sources, get the last version (you need subversion to check the code out, if not yum install subversion):              {noformat} svn checkout svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg cd ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the transcode software Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required to make AVED working, if you provid AVED direcly frames, you can go to the next step. Transcode can be install from a RPM using the yum command, but it is not the basic depot boxes, it can be found on the livna depot that you can download at: [http://rpm.livna.org/rlowiki/]. Download it and install the rpm. Or you can get the code from [http://www.transcoding.org/cgi-bin/transcode]and install it. \\ {noformat} rpm -ivh livna-release-xxxxx.rpm yum install transcode {noformat} If you need to install it from source (rpm transcode are not available for all distributions), first begin by downloading the source from: [http://www.transcoding.org/cgi-bin/transcode], then uncompress the source (bunzip2 is required, if you don't have it: yum install bunzip2). {noformat} bunzip2 transcode-xxxxxx.tar.bz2 tar xvf transcode-xxxxxxx.tar {noformat} Transcode uses shared libraries, here is the list and the RPM packages that provides them:     || Library || RPM Packages || Fedora command \\ || | mpeg2dec | mpeg2dec and mpeg2dec-devel \\ | yum install mpeg2dec; yum install mpeg2dec-devel \\ | | libXv \\ | libXv-devel | yum install libXv-devel \\ |  Then go in the transcode directory: \\ {noformat} cd transcode-xxxxxxx ./configure --disable-lame --disable-libdvdread make sudo make install {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. * Now change to the new directory cd mbarivision * Run configure. You can start with the defaults. If you need to modify the installation parameters you can read the next section. ./configure * Build the code make Install the code * make install \\]]> 5374124 5406873 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the transcode software Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required to make AVED working, if you provid AVED direcly frames, you can go to the next step. Transcode can be install from a RPM using the yum command, but it is not the basic depot boxes, it can be found on the livna depot that you can download at: [http://rpm.livna.org/rlowiki/]. Download it and install the rpm. Or you can get the code from [http://www.transcoding.org/cgi-bin/transcode]and install it. \\ {noformat} rpm -ivh livna-release-xxxxx.rpm yum install transcode {noformat} If you need to install it from source (rpm transcode are not available for all distributions), first begin by downloading the source from: [http://www.transcoding.org/cgi-bin/transcode], then uncompress the source (bunzip2 is required, if you don't have it: yum install bunzip2). {noformat} bunzip2 transcode-xxxxxx.tar.bz2 tar xvf transcode-xxxxxxx.tar {noformat} Transcode uses shared libraries, here is the list and the RPM packages that provides them:     || Library || RPM Packages || Fedora command \\ || | mpeg2dec | mpeg2dec and mpeg2dec-devel \\ | yum install mpeg2dec; yum install mpeg2dec-devel \\ | | libXv \\ | libXv-devel | yum install libXv-devel \\ |  Then go in the transcode directory: \\ {noformat} cd transcode-xxxxxxx ./configure --disable-lame --disable-libdvdread make sudo make install {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. * Now change to the new directory cd mbarivision * Run configure. You can start with the defaults. If you need to modify the installation parameters you can read the next section. ./configure * Build the code make Install the code * make install \\]]> 5374123 5406868 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the transcode software Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required to make AVED working, if you provid AVED direcly frames, you can go to the next step. Transcode can be install from a RPM using the yum command, but it is not the basic depot boxes, it can be found on the livna depot that you can download at: [http://rpm.livna.org/rlowiki/]. Download it and install the rpm. Or you can get the code from [http://www.transcoding.org/cgi-bin/transcode]and install it. \\ {noformat} rpm -ivh livna-release-xxxxx.rpm yum install transcode {noformat} If you need to install it from source (rpm transcode are not available for all distributions), first begin by downloading the source from: [http://www.transcoding.org/cgi-bin/transcode], then uncompress the source (bunzip2 is required, if you don't have it: yum install bunzip2). {noformat} bunzip2 transcode-xxxxxx.tar.bz2 tar xvf transcode-xxxxxxx.tar {noformat} Transcode uses shared libraries, here is the list and the RPM packages that provides them:     || Library || RPM Packages || Fedora command \\ || | mpeg2dec | mpeg2dec and mpeg2dec-devel \\ | yum install mpeg2dec; yum install mpeg2dec-devel \\ | | libXv \\ | libXv-devel | yum install libXv-devel \\ |  Then go in the transcode directory: \\ {noformat} cd transcode-xxxxxxx ./configure --disable-lame --disable-libdvdread make sudo make install {noformat}\\ \\ \\ \\ \\ \\ \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. * Now change to the new directory cd mbarivision * Run configure. You can start with the defaults. If you need to modify the installation parameters you can read the next section. ./configure * Build the code make Install the code * make install \\]]> 5374118 5406863 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the transcode software Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required to make AVED working, if you provid AVED direcly frames, you can go to the next step. Transcode can be install from a RPM using the yum command, but it is not the basic depot boxes, it can be found on the livna depot that you can download at: [http://rpm.livna.org/rlowiki/]. Download it and install the rpm. Or you can get the code from [http://www.transcoding.org/cgi-bin/transcode]and install it. \\ {noformat} rpm -ivh livna-release-xxxxx.rpm yum install transcode {noformat} If you need to install it from source (rpm transcode are not available for all distributions), first begin by downloading the source from: [http://www.transcoding.org/cgi-bin/transcode], then uncompress the source (bunzip2 is required, if you don't have it: yum install bunzip2). {noformat} bunzip2 transcode-xxxxxx.tar.bz2 tar xvf transcode-xxxxxxx.tar {noformat} Transcode uses shared libraries, here is the list and the RPM packages that provides them:     || Library || RPM Packages || Fedora command \\ || | mpeg2dec | mpeg2dec and mpeg2dec-devel \\ | yum install mpeg2dec; yum install mpeg2dec-devel \\ | | libXv \\ | libXv-devel | yum install libXv-devel \\ |  Then go in the transcode directory: \\ {noformat} cd transcode-xxxxxxx ./configure --disable-lame --disable-libdvdread make sudo make install {noformat}\\ \\ \\ \\ \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. \\]]> 5374113 5406866 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h5.     Install The Saliency  When all Saliency dependencies are install, you need to build it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3.  Get and built the transcode software Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required to make AVED working, if you provid AVED direcly frames, you can go to the next step. Transcode can be install from a RPM using the yum command, but it is not the basic depot boxes, it can be found on the livna depot that you can download at: [http://rpm.livna.org/rlowiki/]. Download it and install the rpm. Or you can get the code from [http://www.transcoding.org/cgi-bin/transcode]and install it. \\ {noformat} rpm -ivh livna-release-xxxxx.rpm yum install transcode {noformat} If you need to install it from source (rpm transcode are not available for all distributions), first begin by downloading the source from: [http://www.transcoding.org/cgi-bin/transcode], then uncompress the source (bunzip2 is required, if you don't have it: yum install bunzip2). {noformat} bunzip2 transcode-xxxxxx.tar.bz2 tar xvf transcode-xxxxxxx.tar {noformat} Transcode uses shared libraries, here is the list and the RPM packages that provides them:     || Library || RPM Packages || Fedora command \\ || | mpeg2dec | mpeg2dec and mpeg2dec-devel \\ | yum install mpeg2dec; yum install mpeg2dec-devel \\ | | libXv \\ | libXv-devel | yum install libXv-devel \\ |  Then go in the transcode directory: \\ {noformat} cd transcode-xxxxxxx ./configure --disable-lame --disable-libdvdread make sudo make install {noformat}\\ \\ \\ \\ \\ \\ h3.  Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. * Now change to the new directory cd mbarivision * Run configure. You can start with the defaults. If you need to modify the installation parameters you can read the next section. ./configure * Build the code make Install the code * make install\\]]> 5374116 5406861 5374111 5406862 5374112 5406858 5374107 5406851 5374100 5406854 5374103 5406913 5374165 5406912 5374164 5406911 5374163 5406910 cd src/xerces runConfigure -p linux gmake sudo gmake install {noformat} {color:#990000}TODO: Verify this - is this for mbarivision ? make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib){color} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} hen, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat}]]> 5374162 5406909 cd src/xerces runConfigure -p linux gmake sudo gmake install {noformat} {color:#990000}TODO: Verify this - is this for mbarivision ? make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib){color} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. {noformat} yum install perl-CPAN perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat}]]> 5374161 5406907 Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs.  Download the source code version 2.7 or > from [http://xerces.apache.org/xerces-c/] Untar, and install the xerces-c-srcXXXXX.tar.gz source code with: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} {color:#990000}TODO: Verify this - is this for mbarivision ? make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib){color} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. {noformat} yum install perl-CPAN perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat}]]> 5374159 5406905 Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs.  Download the source code version 2.7 or > from [http://xerces.apache.org/xerces-c/] Untar, and install the xerces-c-srcXXXXX.tar.gz source code with: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib)]]> 5374157 5406903 cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) ]]> 5374155 5406901 5374153 5406900 5374152 5406897 5374148 5406898 ) ** [Xerces-C+\+|http://xerces.apache.org/xerces-c/] (version ) ** XML::Simple perl module(latest version) ** [Transcode|http://www.transcoding.org/cgi-bin/transcode] (optional version 1.0.2 or >) * *Download and uncompress* the AVED source files that are distributed as tar'ed files, then build the source. h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. * Now change to the new directory cd mbarivision * Run configure. You can start with the defaults. If you need to modify the installation parameters you can read the next section. ./configure * Build the code make Install the code * make install \\]]> 5374149 5406896 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the minimal build required for running the AVED software requires that you make _core_ and _tprogs_ with: it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server.]]> 5374147 5406893 ) ** [Xerces-C+\+|http://xerces.apache.org/xerces-c/] (version ) ** XML::Simple perl module(latest version) ** [Transcode|http://www.transcoding.org/cgi-bin/transcode] (optional version 1.0.2 or >) * *Download and uncompress* the AVED source files that are distributed as tar'ed files, then build the source. h3. Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. * Now change to the new directory cd mbarivision * Run configure. You can start with the defaults. If you need to modify the installation parameters you can read the next section. ./configure * Build the code make Install the code * make install \\]]> 5374144 5406892 5374143 5406889 ) ** [Xerces-C+\+|http://xerces.apache.org/xerces-c/] (version ) ** XML::Simple perl module(latest version) ** [Transcode|http://www.transcoding.org/cgi-bin/transcode] (optional version 1.0.2 or >) * *Download and uncompress* the AVED source files that are distributed as tar'ed files, then build the source. h3. Building the Transcode software (optional) Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required for AVED to work if your video is already broken into individual frames. If your video is on a container like an avi, mov, or asf, you might want this tool to convert your video into individual frames for processing. If not, skip this step. Transcode can be install from a RPM using the yum command, but it first must be downloaded from: [http://rpm.livna.org/rlowiki/]. Download it and install the rpm. Or, you can get the source code from [http://www.transcoding.org/cgi-bin/transcode]and install it. \\ {noformat} rpm -ivh livna-release-xxxxx.rpm yum install transcode {noformat} If you need to install it from source (rpm transcode are not available for all distributions), first begin by downloading the source from: [http://www.transcoding.org/cgi-bin/transcode], then uncompress the source. {noformat} bunzip2 transcode-xxxxxx.tar.bz2 tar xvf transcode-xxxxxxx.tar {noformat} Transcode uses shared libraries, here is the list and the RPM packages that provides them:     || Library || RPM Packages || Fedora command \\ || | mpeg2dec | mpeg2dec and mpeg2dec-devel \\ | yum install mpeg2dec; yum install mpeg2dec-devel \\ | | libXv \\ | libXv-devel | yum install libXv-devel \\ |  Then go in the transcode directory and build it: \\ {noformat} cd transcode-xxxxxxx ./configure --disable-lame --disable-libdvdread make sudo make install {noformat}\\ \\ h3. Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. * Now change to the new directory cd mbarivision * Run configure. You can start with the defaults. If you need to modify the installation parameters you can read the next section. ./configure * Build the code make Install the code * make install \\]]> 5374140 5406887 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the minimal build required for running the AVED software requires that you make _core_ and _tprogs_ with: it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ ]]> 5374138 5406885 5374136 5406884 ) ** [Xerces-C+\+|http://xerces.apache.org/xerces-c/] (version ) ** XML::Simple perl module(latest version) ** [Transcode|http://www.transcoding.org/cgi-bin/transcode] (optional version 1.0.2 or >) * *Download and uncompress* the AVED source files that are distributed as tar'ed files, then build the source. h1. Preparation for building the Saliency Toolkit Most importantly, the AVED software requires the Saliency Toolkit from the [ilab|http://ilab.usc.edu/bu/] at Caltech. The Saliency toolkit is distributed as source files, so you must compile it. To get the Toolkit, you must ask for permission to use it by following the instructions on the bottom of this page: [http://ilab.usc.edu/toolkit/downloads.shtml]. Let them know you will be using this with the AVED software from MBARI.   As long are you use the Toolkit for academic or research use, you will be granted access to the code. You will be given a user login and password to check out the code from the ilab SVN repository. If you don't have [Subversion|http://subversion.tigris.org/] installed, you can install it using: {noformat} yum install subversion {noformat} Once you get a username and password, check-out the code using svn: {noformat} svn checkout --username anonsvn svn://iLab.usc.edu/trunk/saliency {noformat} Next, install the library dependencies using yum: || Library || RPM Packages || Fedora command \\ || | libX11 | xorg-x11-proto-devel \\ | yum \-y install xorg-x11-proto-devel | | gcc \\ | gcc-c+\+ | yum \-y install gcc-c+\+ \\ | | tclsh \\ | tclx \\ | yum \-y install tclx \\ | | libXShm \\ | libXext-devel \\ | yum \-y install libXext-devel | | libbz2 | bzip2-devel \\ | yum \-y install bzip2-devel \\ | | libz \\ | zlib-devel | yum \-y install zlib-devel | | lpng \\ | libpng and libpng-devel \\ | yum \-y install libpng; yum \-y install libpng-devel \\ | | ljpeg \\ | libjpeg and libjpeg-devel \\ | yum \-y install libjpeg; yum \-y install libjpeg-devel | | libavcodec, libavutil, libavformat \\ | ffmpeg and ffmpeg-devel or install from sources \\ | | To install ffmpeg from sources, get the last version (you need subversion to check the code out, if not yum install subversion):              {noformat} svn checkout svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg cd ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the minimal build required for running the AVED software requires that you make _core_ and _tprogs_ with: it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. \\ h3. Building the Transcode software (optional) Transcode is a suite of command line utilities for transcoding video, used in this project to get frames from movies. This is not required for AVED to work if your video is already broken into individual frames. If your video is on a container like an avi, mov, or asf, you might want this tool to convert your video into individual frames for processing. If not, skip this step. Transcode can be install from a RPM using the yum command, but it first must be downloaded from: [http://rpm.livna.org/rlowiki/]. Download it and install the rpm. Or, you can get the source code from [http://www.transcoding.org/cgi-bin/transcode]and install it. \\ {noformat} rpm -ivh livna-release-xxxxx.rpm yum install transcode {noformat} If you need to install it from source (rpm transcode are not available for all distributions), first begin by downloading the source from: [http://www.transcoding.org/cgi-bin/transcode], then uncompress the source. {noformat} bunzip2 transcode-xxxxxx.tar.bz2 tar xvf transcode-xxxxxxx.tar {noformat} Transcode uses shared libraries, here is the list and the RPM packages that provides them:     || Library || RPM Packages || Fedora command \\ || | mpeg2dec | mpeg2dec and mpeg2dec-devel \\ | yum install mpeg2dec; yum install mpeg2dec-devel \\ | | libXv \\ | libXv-devel | yum install libXv-devel \\ |  Then go in the transcode directory and build it: \\ {noformat} cd transcode-xxxxxxx ./configure --disable-lame --disable-libdvdread make sudo make install {noformat}\\ \\ h3. Get and built the Xerces C+\+ library Xerces C+\+ is a library allowing AVED to export the results into an XML file. This library provides several utilities to manipulate and to validate XML documents using the DOM and SAX APIs. Download the source code xerces-c-srcXXXXX.tar.gz and untar it, then: \\ {noformat} export XERCESCROOT= cd src/xercesc ./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib) h1. Configure script Configure is script that you run to setup the build environment for the C-compiler. It generates the "Makefile" which the program "make" uses to compile and install the software. Our configure script, for now, is pretty primitif, so we are using envirenmental variable as well, which have to be set: {noformat} export SALIENCYROOT= export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. * Now change to the new directory cd mbarivision * Run configure. You can start with the defaults. If you need to modify the installation parameters you can read the next section. ./configure * Build the code make Install the code * make install \\]]> 5374135 5406946   ./configure make make install  {noformat}  ]]> 5374199 5406931 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | h3.    Exemples  On mbarivision/samples a movie file composed of several frame is provided. The command line exemple are executed from the mbarivision directory. \\ || Goal || Command || Outputs || Comments || | Process a video | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=none \--input-frames=0-99@1 \\ | none \\ | There are several options here. The \--in option says to take input from the named raster file; we support several raster file formats, including png and pnm (ppm/pgm/pbm). The \--out option says we don't want any outputs. When you pass the filename to \--in, put a '#' in the place where the frame number should go. Thus, it will read frame000000.png, frame000001.png. By default, it will keep reading input files until it encounters a missing raster file. If you want it to stop sooner, you can specify a frame range with the \--input-frames option, such as \--input-frames=0-99@1. | | Get a bench of pictures with the events outlined \\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-save-output | Bench of pictures \\ | Same than the previous exemple, but this time the output will be a bench of franes with the events detected outlined by a boundery box. \\ | | Get focussed on benthic animals and save the result into an XML file \\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-cache-size=15 \--mbari-tracking-mode=BoundingBox \--mbari-min-event-area=100 \--mbari-max-event-area=10000 \--mbari-save-events-xml=./benthic.xml \\ | XML file \\ | The tracking mode BoudingBox is using a tracking algorithm which superpose segmentation results. As benthic objects are quite big, we delimited the objects value between \[100-1000\]. The result file is provided in the samples folder as benthic.xml. | h1. Using the scripts \--------------------------------------\- TODO  h1. Using the Graphical User Interface So far, the graphical usr interface is not available, but it will be in the release of next year. \\ \\]]> 5374183 5406934 export XERCESCROOT= export AVED_BIN=/bin {noformat} Use the following step to build the executable from source: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint} If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ran make. As well make allclean will clean the dependencies file generated from a make. You'll want to do this if you update the source code. {tip}]]> 5374186 5406938 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | h3.    Exemples  On mbarivision/samples a movie file composed of several frame is provided. The command line exemple are executed from the mbarivision directory. \\ || Goal || Command || Outputs || Comments || | Process a video | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=none \--input-frames=0-99@1 \\ | none \\ | There are several options here. The \--in option says to take input from the named raster file; we support several raster file formats, including png and pnm (ppm/pgm/pbm). The \--out option says we don't want any outputs. When you pass the filename to \--in, put a '#' in the place where the frame number should go. Thus, it will read frame000000.png, frame000001.png. By default, it will keep reading input files until it encounters a missing raster file. If you want it to stop sooner, you can specify a frame range with the \--input-frames option, such as \--input-frames=0-99@1. | | Get a bench of pictures with the events outlined \\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-save-output | Bench of pictures \\ | Same than the previous exemple, but this time the output will be a bench of franes with the events detected outlined by a boundery box. \\ | | Get focussed on benthic animals and save the result into an XML file \\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-cache-size=15 \--mbari-tracking-mode=BoundingBox \--mbari-min-event-area=100 \--mbari-max-event-area=10000 \--mbari-save-events-xml=./benthic.xml \\ | XML file \\ | The tracking mode BoudingBox is using a tracking algorithm which superpose segmentation results. As benthic objects are quite big, we delimited the objects value between \[100-1000\]. The result file is provided in the samples folder as benthic.xml. | h1. Using the scripts \--------------------------------------\- TODO  h1. Using the Graphical User Interface So far, the graphical usr interface is not available, but it will be in the release of next year. \\ \\]]> 5374191 5406937 export XERCESCROOT= export AVED_BIN=/bin {noformat} Use the following step to build the executable from source: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint} If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ran make. As well make allclean will clean the dependencies file generated from a make. You'll want to do this if you update the source code. {tip}]]> 5374190 5406924 export XERCESCROOT= export AVED_BIN=/bin {noformat} Use the following step to build the executable from source: {noformat} cd ./configure make make install {noformat} {hint:title=Handy Hint} If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. {hint}]]> 5374176 21397550 /dev/null 2>&1 #on the first of every month, remove files older than 90 days 00 00 01 * * /usr/local/bin/cleanscratchfiles #at midnight daily rebuild scratch in case new users added or permissions changed 59 23 * * * /usr/local/bin/buildscratch #check disk space every hour and send root alert if getting too full 0 * * * * /usr/local/bin/diskalert {noformat} diskalert {noformat} #!/bin/sh # set -x # Shell script to monitor or watch the disk space # It will send an email to $ADMIN, if the (free available) percentage of space is >= 90%. # ------------------------------------------------------------------------- # Set admin email so that you can get email. ADMIN="root" # set alert level 90% is default ALERT=90 # Exclude list of unwanted monitoring, if several partions then use "|" to separate the partitions. # An example: EXCLUDE_LIST="/dev/hdd1|/dev/hdc5" EXCLUDE_LIST="tempest:/users|tempest:/tempbox:tornado:/Engineering|tornado:/vol/vol1/ProjectLibrary|nanomia.private.net:/nanomiaRAID" # #:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: # function main_prog() { while read output; do #echo $output usep=$(echo $output | awk '{ print $1}' | cut -d'%' -f1) partition=$(echo $output | awk '{print $2}') if [ $usep -ge $ALERT ] ; then echo "Running out of space \"$partition ($usep%)\" on server $(hostname), $(date)" | mail -s "ALERT: Almost out of disk space $usep% on $(hostname)" $ADMIN fi done } if [ "$EXCLUDE_LIST" != "" ] ; then df -lH | grep -vE "^Filesystem|tmpfs|cdrom|${EXCLUDE_LIST}" | awk '{print $5 " " $6}' | main_prog else df -lH | grep -vE "^Filesystem|tmpfs|cdrom" | awk '{print $5 " " $6}' | main_prog fi {noformat} buildscratch {noformat} ! /bin/bash #set -x USERID=`id -u` if [ $USERID != 0 ]; then echo "You must be root to rue buildscratch" exit 0 fi function dowork() { echo "Building $1" #remove all directories and recreate using file containing users users=$(cat /etc/passwd |grep 20| cut -f1 -d ":") pushd /mnt/scratch #change permissions to include all users chmod a+rwx /mnt/scratch #change owner for new directories for dir in $users do if [ ! -d $dir ]; then echo "mkdir $dir" mkdir $dir fi echo "chown $dir:users $dir" chown $dir:users $dir echo "chmod 0777 $dir " chmod 777 $dir done chown aved:aved aved popd #refresh scratch space NFS mounts on all nodes #cexec '/bin/umount /mnt/scratch;/bin/mount /mnt/scratch' } for s in "/mnt/scratch" "/mnt/scratch2" do dowork $s done #rebuild video directories for capture echo "Rebuilding video capture directories" if [ ! -d /mnt/scratch/video ]; then mkdir -p /mnt/scratch/video/capture fi chmod -Rf a+rwx /mnt/scratch/video #rebuild directories for condor if [ ! -d /mnt/scratch/condor ]; then mkdir -p /mnt/scratch/condor -m=0755 fi chown daemon:root /mnt/scratch/condor {noformat} h2. RAID format Install xfsprogs {noformat} yum install xfsprogs {noformat} Reformat NSTOR RAID {noformat} fdisk /dev/sda pvcreate /dev/sda vgdisplay lvcreate -i2 -I4 -l 2198.7G -namedev AVEDRAID {noformat} Reformat RAID filesystem to XFS {noformat} mkfs.xfs -f - L "AVEDRAID" /dev/sda {noformat}]]> 21364783 21397551 21364784 11830038 11797294 5406928 export XERCESCROOT= export AVED_BIN=/bin {noformat} Use the following step to build the executable from source: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint} If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ran make. As well make allclean will clean the dependencies file generated from a make. You'll want to do this if you update the source code. {tip}]]> 5374181 5406915 ) ** [Xerces-C+\+|http://xerces.apache.org/xerces-c/] (version ) ** XML::Simple perl module(latest version) ** [Transcode|http://www.transcoding.org/cgi-bin/transcode] (optional version 1.0.2 or >) * *Download and uncompress* the AVED source files that are distributed as tar'ed files, then build the source. ]]> 5374167 5406917 ** [Xerces-C+\+|http://xerces.apache.org/xerces-c/] ({color:#990000}version{color} {color:#990000}TBD){color} ** XML::Simple perl module (latest version) ** [Transcode|http://www.transcoding.org/cgi-bin/transcode] version 1.0.2 or > (optional) * *Download and uncompress* the AVED source files that are distributed as tar'ed files, then build the source.]]> 5374169 5406919 export XERCESCROOT= export AVED_BIN=/bin {noformat} To run configure your current directory must be the mbarivision directory. You type {noformat} ./configure {noformat} You can add the parameter ./configure \--help to get help on the different switches. This is walk through of the options.            ......................................................... TODO add all the configure parameters \\ \\ \\ h1. Make When you run make, all the C++-source files are automatically compiled and linked. Just look out for error messages. Make uses a file called "Makefile" which is generated by the "configure" script you just ran.  Attention\! If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. * Now change to the new directory cd mbarivision * Run configure. You can start with the defaults. If you need to modify the installation parameters you can read the next section. ./configure * Build the code make Install the code * make install \\]]> 5374171 5406921 export XERCESCROOT= export AVED_BIN=/bin {noformat} Use the following step to build the executable from source: {noformat} cd ./configure make make install {noformat} {note:title=Handy Hint} If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ranmake. As well amakeallclean will clean the dependencies file generated from a make. {note}]]> 5374173 11830043 11797299 5406974 5374231 5406973 5374230 5406971 5374228 9405072 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the minimal build required for running the AVED software requires that you make _core_ and _tprogs_ with: {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 9372339 5406977 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the minimal build required for running the AVED software requires that you make _core_ and _tprogs_ with: it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server.]]> 5374234 5406975 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the minimal build required for running the AVED software requires that you make _core_ and _tprogs_ with: it:                                                    {noformat} cd ./configure --enable-quitecompile --without-qtdir --enable-force32 make core make tprogs {noformat} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server.]]> 5374232 5406966 5374223 5406963 ./configure make make install {noformat}\\ \\ \\]]> 5374218 5406970 5374227 5406957 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} {info:title=}Make sure in /opt/condor-xxxxxx/etc/condor_config line reads: DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD {info} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat} h3.     Configuring Condor Change the following value in the /opt/condor-xxxxxxx/local.xxxxxx/condor_config.local {noformat} ## When is this machine willing to start a job? START = TRUE ## When to suspend a job? SUSPEND = FALSE ## When to nicely stop a job? ## (as opposed to killing it instantaneously) PREEMPT = FALSE ## When to instantaneously kill a preempting job ## (e.g. if a job is in the pre-empting stage for too long) KILL = FALSE {noformat}\\ \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.     Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat} h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ h3.     Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ The web service provided condains the service (src/org/mbari/aved/webservice/server/AvedService.java) and an exemple to request it (src/org/mbari/aved/webservice/client/AvedClient.java). Before deploying the web-service, you have to edit the java code in order to provide the user Condor is gonna run with and the computer sets. For that edit the file AvedService.java in src/org/mbari/aved/webservice/server {noformat} public static String SCHEDD_LOCATION = "http://host.domain.name.org:8181"; public static String USER = "aved"; {noformat} Then, compile the source by tapping {noformat} ant {noformat} If everything is going well, you should see a BUILD SUCCESSFULL printed, and a build folder should have been created. In these folder you'll find a AvedService.aar file what is the web-service \! To deploy it, just copy and past this file into your application server directory, and the jars from the jars into the application server lib directory: {noformat} cp build/AvedService.aar /webapps/axis2/WEB-INF/services/ cp jars/*.jar /webapps/axis2/WEB-INF/lib/ {noformat} Restart tomcat, and check with your browser if your web-service is up by tapping [http://host:8080/axis2/services/listServices], AvedService should be listed. The AVED web-service requires 4 envirenmental variables: {noformat} export MBARIVISIONROOT= export JAVA_HOME= export CONDOR_CONFIG=/opt/condor-xxxxxxxxx/etc/condor_config export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} You can know test it with the client code provided \! \\ The web service is composed of 3 functions:             - OMElement sendJobToAved (String path): this function takes for parameter the path of the video to be processed and return an XML file with node1=the cluster number and node2=the job number             - OMElement getJobStatus (int cluster, int job): this function takes the cluster number and the job number and return the job status (1: Idle, 2:Running, 3:Removed, 4:Completed, 5:Held).             - OMElement getResult (int cluster, int job): this function takes the cluster number and the job number and return the XML result of the processing. The web service client is basicly a java code what send a job to AVED wait until the status id is at 4 (completed) and get the result. \\ \\ h3.     Installing the AVED web-service as a service on Linux * Create tomcat.sh file in /etc/profile.d then add the following to it: {noformat} export JAVA_HOME= export MBARIVISIONROOT= export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} * Create tomcat file in /etc/init.d then add the following to it: {noformat} . /etc/profile.d/tomcat.sh /bin/catalina.sh start {noformat} \* Add soft links to the tomcat startup script {noformat} ln -s /etc/init.d/tomcat /etc/rc2.d/S100tomcat ln -s /etc/init.d/tomcat /etc/rc2.d/K100tomcat {noformat} Start the tomcat service \\ {noformat} service tomcat start {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 5374212 5406958 export XERCESCROOT= export AVED_BIN=/bin {noformat} Use the following step to build the executable from source: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint} If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ran make. As well make allclean will clean the dependencies file generated from a make. You'll want to do this if you update the source code. {tip}]]> 5374213 5406955 5374209 5406962 5374217 5406959 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | h3.    Exemples  On mbarivision/samples a movie file composed of several frame is provided. The command line exemple are executed from the mbarivision directory. \\ || Goal || Command || Outputs || Comments || | Process a video | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=none \--input-frames=0-99@1 \\ | none \\ | There are several options here. The \--in option says to take input from the named raster file; we support several raster file formats, including png and pnm (ppm/pgm/pbm). The \--out option says we don't want any outputs. When you pass the filename to \--in, put a '#' in the place where the frame number should go. Thus, it will read frame000000.png, frame000001.png. By default, it will keep reading input files until it encounters a missing raster file. If you want it to stop sooner, you can specify a frame range with the \--input-frames option, such as \--input-frames=0-99@1. | | Get a bench of pictures with the events outlined \\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-save-output | Bench of pictures \\ | Same than the previous exemple, but this time the output will be a bench of franes with the events detected outlined by a boundery box. \\ | | Get focussed on benthic animals and save the result into an XML file \\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-cache-size=15 \--mbari-tracking-mode=BoundingBox \--mbari-min-event-area=100 \--mbari-max-event-area=10000 \--mbari-save-events-xml=./benthic.xml \\ | XML file \\ | The tracking mode BoudingBox is using a tracking algorithm which superpose segmentation results. As benthic objects are quite big, we delimited the objects value between \[100-1000\]. The result file is provided in the samples folder as benthic.xml. | h1.]]> 5374214 5406960 5374215 5406949 5374202 5406950 ./configure make make install {noformat}\\ \\]]> 5374203 5406947 ./configure make make install {noformat}\\]]> 5374200 5406948 cd src/xerces runConfigure -p linux gmake sudo gmake install {noformat} {color:#990000}TODO: Verify this - is this for mbarivision ? make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib){color} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat}]]> 5374201 5406953 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} {info:title=}Make sure in /opt/condor-xxxxxx/etc/condor_config line reads: DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD {info} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat} h3.     Configuring Condor Change the following value in the /opt/condor-xxxxxxx/local.xxxxxx/condor_config.local {noformat} ## When is this machine willing to start a job? START = TRUE ## When to suspend a job? SUSPEND = FALSE ## When to nicely stop a job? ## (as opposed to killing it instantaneously) PREEMPT = FALSE ## When to instantaneously kill a preempting job ## (e.g. if a job is in the pre-empting stage for too long) KILL = FALSE {noformat}\\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.     Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat} h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ h3.     Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ The web service provided condains the service (src/org/mbari/aved/webservice/server/AvedService.java) and an exemple to request it (src/org/mbari/aved/webservice/client/AvedClient.java). Before deploying the web-service, you have to edit the java code in order to provide the user Condor is gonna run with and the computer sets. For that edit the file AvedService.java in src/org/mbari/aved/webservice/server {noformat} public static String SCHEDD_LOCATION = "http://host.domain.name.org:8181"; public static String USER = "aved"; {noformat} Then, compile the source by tapping {noformat} ant {noformat} If everything is going well, you should see a BUILD SUCCESSFULL printed, and a build folder should have been created. In these folder you'll find a AvedService.aar file what is the web-service \! To deploy it, just copy and past this file into your application server directory, and the jars from the jars into the application server lib directory: {noformat} cp build/AvedService.aar /webapps/axis2/WEB-INF/services/ cp jars/*.jar /webapps/axis2/WEB-INF/lib/ {noformat} Restart tomcat, and check with your browser if your web-service is up by tapping [http://host:8080/axis2/services/listServices], AvedService should be listed. The AVED web-service requires 4 envirenmental variables: {noformat} export MBARIVISIONROOT= export JAVA_HOME= export CONDOR_CONFIG=/opt/condor-xxxxxxxxx/etc/condor_config export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} You can know test it with the client code provided \! \\ The web service is composed of 3 functions:             - OMElement sendJobToAved (String path): this function takes for parameter the path of the video to be processed and return an XML file with node1=the cluster number and node2=the job number             - OMElement getJobStatus (int cluster, int job): this function takes the cluster number and the job number and return the job status (1: Idle, 2:Running, 3:Removed, 4:Completed, 5:Held).             - OMElement getResult (int cluster, int job): this function takes the cluster number and the job number and return the XML result of the processing. The web service client is basicly a java code what send a job to AVED wait until the status id is at 4 (completed) and get the result. \\ \\ h3.     Installing the AVED web-service as a service on Linux * Create tomcat.sh file in /etc/profile.d then add the following to it: {noformat} export JAVA_HOME= export MBARIVISIONROOT= export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} * Create tomcat file in /etc/init.d then add the following to it: {noformat} . /etc/profile.d/tomcat.sh /bin/catalina.sh start {noformat} \* Add soft links to the tomcat startup script {noformat} ln -s /etc/init.d/tomcat /etc/rc2.d/S100tomcat ln -s /etc/init.d/tomcat /etc/rc2.d/K100tomcat {noformat} Start the tomcat service \\ {noformat} service tomcat start {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\]]> 5374206 5406952 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | h3.    Exemples  On mbarivision/samples a movie file composed of several frame is provided. The command line exemple are executed from the mbarivision directory. \\ || Goal || Command || Outputs || Comments || | Process a video | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=none \--input-frames=0-99@1 \\ | none \\ | There are several options here. The \--in option says to take input from the named raster file; we support several raster file formats, including png and pnm (ppm/pgm/pbm). The \--out option says we don't want any outputs. When you pass the filename to \--in, put a '#' in the place where the frame number should go. Thus, it will read frame000000.png, frame000001.png. By default, it will keep reading input files until it encounters a missing raster file. If you want it to stop sooner, you can specify a frame range with the \--input-frames option, such as \--input-frames=0-99@1. | | Get a bench of pictures with the events outlined \\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-save-output | Bench of pictures \\ | Same than the previous exemple, but this time the output will be a bench of franes with the events detected outlined by a boundery box. \\ | | Get focussed on benthic animals and save the result into an XML file \\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-cache-size=15 \--mbari-tracking-mode=BoundingBox \--mbari-min-event-area=100 \--mbari-max-event-area=10000 \--mbari-save-events-xml=./benthic.xml \\ | XML file \\ | The tracking mode BoudingBox is using a tracking algorithm which superpose segmentation results. As benthic objects are quite big, we delimited the objects value between \[100-1000\]. The result file is provided in the samples folder as benthic.xml. | h1.]]> 5374205 9405045 ./configure make make install {noformat} When you are done, complete installation with [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts].\\ \\ \\ \\ \\ \\ \\]]> 9372312 9405044 cd $XERCESCROOT/src/xerces runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software (optional)]]]> 9372311 714 717 6226560 6259357 1867816 [^SourceMetaData.xsd] and references \--------> [^EventDetectionParameters.xsd]]]> 1835052 5406835 5374081 5406842 5374089 1867781 1835013 5406846 5374094 1867780 1835012 5406848 5374096 1867806 [^SourceMetaData.xsd] uses ------> [^EventDetectionParameters.xsd] [AVED Source Metadata Example|^20070706T123100.avi.metadata.xml]\[this was based on an old version and no longer represents the current metadata\]]]> 1835038 1867805 1835037 1867804 1835036 1867808 [^SourceMetaData.xsd] and references ---> [^EventDetectionParameters.xsd] [AVED Source Metadata Example|^20070706T123100.avi.metadata.xml]\[this was based on an old version and no longer represents the current metadata\]]]> 1835040 1867807 [^SourceMetaData.xsd] and references \------> [^EventDetectionParameters.xsd] [AVED Source Metadata Example|^20070706T123100.avi.metadata.xml]\[this was based on an old version and no longer represents the current metadata\]]]> 1835039 5406834 5374080 5406832 5374078 11796572 11829334 1 2007-01-30 09:44:32.397 2007-01-30 09:44:32.397 717 5407118 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  AVED was installed as the user root. An additional account was setup for a user aved. Passwords for both have been delivered to Dhugal. h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Some are still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the table JAMSTEC Custom Scripts table below.  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139.mov | Quicktime movie encoded with mpeg4 codec.  \\ This was was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] \\ date and time convention because this is used by AVED scripts to timestamp events. \\ E.g. assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. | cd /home/aved/Video/20080604T063139.mov; jamstec_runprocess 20080604T063139.mov | h3. JAMSTEC Custom Scripts || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages and runs the mbarivis_command. Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only process the first 100 frames of the clip, so change if you want to process the entire clip. \\ | \\]]> 5374379 5407116 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  AVED was installed as the user root. An additional account was setup for a user aved. Passwords for both have been delivered to Dhugal. h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Some are still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided, in addition to the AVED scripts, to give examples of how to process the data.  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | \\ | \\ | | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | | | | /home/aved/Video/20080604T063139.mov | Quicktime movie encoded with mpeg4 codec.  \\ This was was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] \\ date and time convention because this is used by AVED scripts to timestamp events. \\ E.g. assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. | cd /home/aved/Video/20080604T063139.mov; jamstec_runprocess 20080604T063139.mov | h3. JAMSTEC Custom Scripts || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages and runs the mbarivis_command. Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only process the first 100 frames of the clip, so change if you want to process the entire clip. \\ | \\]]> 5374377 5407113 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  AVED was installed as the user root. An additional account was setup for a user aved. Passwords for both have been delivered to Dhugal. h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Some are still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided, in addition to the AVED scripts, to give examples of how to process the data.  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. |cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. | | | /home/aved/Video/20080604T063139.mov | Quicktime movie encoded with mpeg4 codec.  \\ This was was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] \\ date and time convention because this is used by AVED scripts to timestamp events. \\ E.g. assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. | | h3. JAMSTEC Custom Scripts || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages and runs the mbarivis_command. Also rescales the input to 640x480 to make the display more manageable. \\ | | \\ | | \\]]> 5374374 5407114 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  AVED was installed as the user root. An additional account was setup for a user aved. Passwords for both have been delivered to Dhugal. h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Some are still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided, in addition to the AVED scripts, to give examples of how to process the data.  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | \\ | \\ | | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | | | | /home/aved/Video/20080604T063139.mov | Quicktime movie encoded with mpeg4 codec.  \\ This was was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] \\ date and time convention because this is used by AVED scripts to timestamp events. \\ E.g. assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. | cd /home/aved/Video/20080604T063139.mov; jamstec_runprocess 20080604T063139.mov | h3. JAMSTEC Custom Scripts || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages and runs the mbarivis_command. Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only process the first 100 frames of the clip, so change if you want to process the entire clip. \\ | \\]]> 5374375 5407111 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  AVED was installed as the user root. An additional account was setup for a user aved. Passwords for both have been delivered to Dhugal. h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Some are still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided, in addition to the AVED scripts, to give examples of how to process the data.  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type \\ || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a \\ PICASSO benthic video recording. \\ Frames were extracted from HD tape. | {noformat} {noformat} | \\ {code} cd /home/aved/Pictures/benthic/benthic_a jamstec_runmbarivis or jamstec_runmbarivis_displayalg {code} \| \\ | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a \\ PICASSO fast moving midwater video recording.  \\ Frames were extracted from a HD tape. | \\ {code} cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect jamstec_runmbarivis or jamstec_runmbarivis_displayalg {code} \| \\ | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording.  \\ Frames were extracted from a HD tape. | | | /home/aved/Video/20080604T063139.mov | Quicktime movie encoded with mpeg4 codec.  \\ This was was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] \\ date and time convention because this is used by AVED scripts to timestamp events. \\ E.g. assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. | | \\ \\ | \\ | \\ | | \\ | \\ | h3. JAMSTEC Custom Scripts || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages and runs the mbarivis_command. Also rescales the input to 640x480 to make the display more manageable. \\ | | \\ | | \\]]> 5374372 5407138 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed to use. Passwords for both the root and aved users have been sent to Dhugal. h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139.mov {tip:title=Handy Hint} This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]\\ date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number. E.g. 20080604T063139 assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} \\ | Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. \\ \\ | cd /home/aved/Video/20080604T063139.mov; jamstec_runprocess 20080604T063139.mov | h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 5374399 5407136 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  The AVED software and its dependencies were installed as the user root. Additionally, a user aved was installed to use. Passwords for both the root and aved users have been delivered to Dhugal. h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Some are still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the table JAMSTEC Custom Scripts table below.  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139.mov | Quicktime movie encoded with mpeg4 codec.  \\ This was was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] \\ date and time convention because this is used by AVED scripts to timestamp events. \\ E.g. assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. | cd /home/aved/Video/20080604T063139.mov; jamstec_runprocess 20080604T063139.mov | h3. JAMSTEC Custom Scripts The following are some simple scripts   || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages and runs the mbarivis_command. Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only process the first 100 frames of the clip, so change if you want to process the entire clip. \\ | \\]]> 5374397 5407154 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ |]]> 5374418 5407147 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h2. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have compiled over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 5374408 5407143 5374404 5407139 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed, intended for use to run AVED. Passwords for both the root and aved users have been sent to Dhugal. h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139.mov \\ {tip:title=Handy Hint}This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]\\ date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number.\\ E.g. 20080604T063139 assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} \\ | Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. \\ \\ | cd /home/aved/Video/20080604T063139.mov; jamstec_runprocess 20080604T063139.mov | h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 5374400 5407140 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed, intended for use to run AVED. Passwords for both the root and aved users have been sent to Dhugal. h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139.mov \\ | \\ {tip:title=Handy Hint}This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number. \\ E.g. 20080604T063139 assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} \\ \| Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. \\ \\ \| cd /home/aved/Video/20080604T063139.mov; jamstec_runprocess 20080604T063139.mov \| \\ h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 5374401 5407163 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed to use. Passwords for both the root and aved users have been sent to Dhugal. A few additional steps were required for this installation: # Add manual links for the dc1394 control libraries. This was needed to get saliency to compile. {noformat} cd /usr/lib ln -s libdc1394.so.22 libdc1394_control.so ln -s libdc1394.so.22 libdc1394.so {noformat} # Add /usr/local/lib to the /etc/ld.so.conf. This was needed to get the loader to load the dependent libraries (e.g. xercesc) that are by default installed to /usr/local/lib to load. {noformat} echo /usr/local/lib >> /etc/ld.so.conf {noformat}\\ \\ h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139.mov \\ | {tip:title=Handy Hint}This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]\\ date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number. \\ E.g. 20080604T063139 assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} \\ \| Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. \\ \\ \| cd /home/aved/Video/20080604T063139.mov; jamstec_runprocess 20080604T063139.mov \| h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 5374427 5407166 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed to use. Passwords for both the root and aved users have been sent to Dhugal. Two additional steps were required for this installation: # Add manual links for the dc1394 control libraries. This was needed to get saliency to compile. {noformat} cd /usr/lib ln -s libdc1394.so.22 libdc1394_control.so ln -s libdc1394.so.22 libdc1394.so {noformat} # Add /usr/local/lib to the /etc/ld.so.conf. This was needed to get the loader to load the dependent libraries (e.g. xercesc) that are by default installed to /usr/local/lib to load. {noformat} echo /usr/local/lib >> /etc/ld.so.conf {noformat}\\ \\ h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139Z.mov \\ | {tip:title=Handy Hint}This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]\\ date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number. \\ E.g. 20080604T063139Z assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} \\ \| Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. \\ \\ \| cd /home/aved/Video/20080604T063139Z.mov; jamstec_runprocess 20080604T063139Z.mov \| h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 5374430 5407165 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed to use. Passwords for both the root and aved users have been sent to Dhugal. Two additional steps were required for this installation: # Add manual links for the dc1394 control libraries. This was needed to get saliency to compile. {noformat} cd /usr/lib ln -s libdc1394.so.22 libdc1394_control.so ln -s libdc1394.so.22 libdc1394.so {noformat} # Add /usr/local/lib to the /etc/ld.so.conf. This was needed to get the loader to load the dependent libraries (e.g. xercesc) that are by default installed to /usr/local/lib to load. {noformat} echo /usr/local/lib >> /etc/ld.so.conf {noformat}\\ \\ h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139.mov \\ | {tip:title=Handy Hint}This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]\\ date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number. \\ E.g. 20080604T063139 assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} \\ \| Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. \\ \\ \| cd /home/aved/Video/20080604T063139.mov; jamstec_runprocess 20080604T063139.mov \| h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 5374429 5407160 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed to use. Passwords for both the root and aved users have been sent to Dhugal. h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139.mov {tip:title=Handy Hint} This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]\\ date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number. E.g. 20080604T063139 assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} \\ | Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. \\ \\ | cd /home/aved/Video/20080604T063139.mov; jamstec_runprocess 20080604T063139.mov | h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 5374424 5407162 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed to use. Passwords for both the root and aved users have been sent to Dhugal. The only additional steps needed were to create some manual links for the dc1394 control libraries. This was needed to get saliency to compile. Here is what we did: {noformat} cd /usr/lib  ln -s libdc1394.so.22 libdc1394_control.so ln -s libdc1394.so.22 libdc1394.so {noformat} h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139.mov \\ {tip:title=Handy Hint}This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]\\ date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number.\\ E.g. 20080604T063139 assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} \\ | Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. \\ \\ | cd /home/aved/Video/20080604T063139.mov; jamstec_runprocess 20080604T063139.mov | h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 5374426 5407156 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | | \--mbari-saliency-dist=\\ | \[5\] \\ | The number of frames to delay between saliency map computations. Reduce this to improve your detection rate. Warning - this will increase your computation time. \\ |]]> 5374420 5407158 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | | \--mbari-saliency-dist= \\ | \[5\] \\ | The number of frames to delay between saliency map computations. Reduce this to improve your detection rate. Warning - this will increase your computation time. \\ |]]> 5374422 11829784 11797030 11829786 11797032 11829785 cp make install mpeg_encode /usr/local/bin {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision and AVED scripts|mbarivision Installation - Step 6. Build and Install mbarivision]. \\ \\ \\ \\ \\ \\ \\]]> 11797031 11829780 11797026 11829792 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 11797038 11829794 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVEDac Installation].  The AVED software and its dependencies were installed as the user *root*. Additionally, a user *aved* was installed to use. Passwords for both the root and aved users have been sent to Dhugal. Two additional steps were required for this installation: # Add manual links for the dc1394 control libraries. This was needed to get saliency to compile. {noformat} cd /usr/lib ln -s libdc1394.so.22 libdc1394_control.so ln -s libdc1394.so.22 libdc1394.so {noformat} # Add /usr/local/lib to the /etc/ld.so.conf. This was needed to get the loader to load the dependent libraries (e.g. xercesc) that are by default installed to /usr/local/lib to load. {noformat} echo /usr/local/lib >> /etc/ld.so.conf {noformat}\\ \\ h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Two are sets of still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided in addition to the AVED scripts, to give examples of how to process the data. These scripts are noted in the JAMSTEC Scripts table below .  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording. Frames were extracted from HD tape. | cd /home/aved/Pictures/benthic/benthic_a \\ jamstec_runmbarivis_displayalg \\ \\ This will display output, similar to the following. \*NOTE\* Windows display overlapped, not in the cascade pattern shown in this image. Just remember to click and drag them from on top of each other. \\ (click to enlarge)  !ScreenshotAlgorithmRunning.png|thumbnail!\\ \\ OR \\ jamstec_runmbarivis  \\ This will simply spew out the output from mbarivision into the console window.  \\ (click to enlarge)  !ScreenshotJamstecrunmbarivis.png|thumbnail!\\ \\ | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording. Frames were extracted from a HD tape. | cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect \\ jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording. \\ Frames were extracted from a HD tape. \\ | cd /home/aved/Pictures/midwater/midwater/midwater_slowtransect; jamstec_runmbarivis or jamstec_runmbarivis_displayalg | | /home/aved/Video/20080604T063139Z.mov \\ {tip:title=Handy Hint}This file was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]\\ date and time convention as the ISO standard is used by AVED scripts to timestamp events by timecode, instead of frame number. \\ E.g. 20080604T063139Z assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. {tip} | Quicktime movie encoded with mpeg4 codec.  Source was received via FTP from Dhugal. | cd /home/aved/Video/20080604T063139Z.mov; jamstec_runprocess 20080604T063139Z.mov \\ | h3. JAMSTEC Scripts The following are some simple scripts to help get you started:  || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. *This must be executed in the root directory of the ppm frames*, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages. *This must be executed in the root directory of the ppm frames*, Also rescales the input to 640x480 to make the display more manageable. \\ | | /home/aved/jamstec_runprocess | Simple wrapper script that executes the runclip AVED script, and displays the output in the vlc viewer. Only processes the first 100 frames of the clip, so remove the argument that specifies the frame range, and by default this will process the entire clip. \\ | \\]]> 11797041 11829793 11797040 11829788 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is diminishing, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat} When you are done, you can skip to [step 6|mbarivision Installation - Step 6. Build and Install mbarivision], or continue to the next optional step [AVED Installation - Step 5. Build and install Berkeley MPEG Encoder|mbarivision Installation - Step 5. Build and install Berkeley MPEG Encoder (optional)]\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 11797034 11829787 export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} {tip:title=Handy Hint} If you installed the Xerces C+\+ library to a non-standard library location, be sure to add to the loader path in /etc/ld.so.conf the location, and run ldconfig -v to refresh the loader. {tip} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|mbarivision Installation - Step 6. Build and Install mbarivision], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|mbarivision Installation - Step 3. Build and Install Transcode and mpeg4ip Software].]]> 11797033 11829790 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 11797036 11829789 11797035 11829764 11797010 11829774 11797020 11829799 11797046 11829797 11797044 11829795 11797042 5406985 5374242 5406983 5374240 5406982 5374239 5406981 5374238 5406994 5374251 5406992 5374249 5406990 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | h3.    Exemples  On mbarivision/samples a movie file composed of several frame is provided. The command line exemple are executed from the mbarivision directory. \\ || Goal || Command || Outputs || Comments || | Process a video | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=none \--input-frames=0-99@1 \\ | none \\ | There are several options here. The \--in option says to take input from the named raster file; we support several raster file formats, including png and pnm (ppm/pgm/pbm). The \--out option says we don't want any outputs. When you pass the filename to \--in, put a '#' in the place where the frame number should go. Thus, it will read frame000000.png, frame000001.png. By default, it will keep reading input files until it encounters a missing raster file. If you want it to stop sooner, you can specify a frame range with the \--input-frames option, such as \--input-frames=0-99@1. | | Get a bench of pictures with the events outlined \\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-save-output | Bench of pictures \\ | Same than the previous exemple, but this time the output will be a bench of franes with the events detected outlined by a boundery box. \\ | | Get focussed on benthic animals and save the result into an XML file \\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-cache-size=15 \--mbari-tracking-mode=BoundingBox \--mbari-min-event-area=100 \--mbari-max-event-area=10000 \--mbari-save-events-xml=./benthic.xml \\ | XML file \\ | The tracking mode BoudingBox is using a tracking algorithm which superpose segmentation results. As benthic objects are quite big, we delimited the objects value between \[100-1000\]. The result file is provided in the samples folder as benthic.xml. | h1.]]> 5374247 5406989 5374246 5406987 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | h3.    Exemples  On mbarivision/samples a movie file composed of several frame is provided. The command line exemple are executed from the mbarivision directory. \\ || Goal || Command || Outputs || Comments || | Process a video | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=none \--input-frames=0-99@1 \\ | none \\ | There are several options here. The \--in option says to take input from the named raster file; we support several raster file formats, including png and pnm (ppm/pgm/pbm). The \--out option says we don't want any outputs. When you pass the filename to \--in, put a '#' in the place where the frame number should go. Thus, it will read frame000000.png, frame000001.png. By default, it will keep reading input files until it encounters a missing raster file. If you want it to stop sooner, you can specify a frame range with the \--input-frames option, such as \--input-frames=0-99@1. | | Get a bench of pictures with the events outlined \\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-save-output | Bench of pictures \\ | Same than the previous exemple, but this time the output will be a bench of franes with the events detected outlined by a boundery box. \\ | | Get focussed on benthic animals and save the result into an XML file \\ | ./bin/mbarivision \--in=raster:samples/f#.ppm \--out=display \--input-frames=0-99@1 \--mbari-cache-size=15 \--mbari-tracking-mode=BoundingBox \--mbari-min-event-area=100 \--mbari-max-event-area=10000 \--mbari-save-events-xml=./benthic.xml \\ | XML file \\ | The tracking mode BoudingBox is using a tracking algorithm which superpose segmentation results. As benthic objects are quite big, we delimited the objects value between \[100-1000\]. The result file is provided in the samples folder as benthic.xml. | h1.]]> 5374244 5407002 ** [Xerces-C+\+ and perl XML modules|http://xerces.apache.org/xerces-c/] ({color:#990000}version{color} {color:#990000}TBD){color} ** [Transcode|http://www.transcoding.org/cgi-bin/transcode] version 1.0.2 or > (optional) ** OpenQuicktime (optional) ** Berkeley MPEG-1 encoder (optional) * *Download and uncompress* the AVED source files that are distributed as tar'ed files, then build the source.]]> 5374259 5407000 5374257 5406998 5374255 5407009 ** [Xerces-C+\+ and perl XML modules|http://xerces.apache.org/xerces-c/] ({color:#990000}version{color} {color:#990000}TBD){color} ** [Transcode|http://www.transcoding.org/cgi-bin/transcode] version 1.0.2 or > (optional) ** OpenQuicktime (optional) ** Berkeley MPEG-1 encoder (optional) * *Download and uncompress* the AVED source files that are distributed as tar'ed files, then build the source. The detailed steps to install AVED are: # [AVED Installation - Step 1. Build iLab Saliency Toolkit] # [AVED Installation - Step 2. Build and Install XML Libraries] # [AVED Installation - Step 3. Build and Install Transcode Software (optional)] # [AVED Installation - Step 4. Build and install Berkeley MPEG Encoder (optional)]  ]]> 5374266 5407010 ** [Xerces-C+\+ and perl XML modules|http://xerces.apache.org/xerces-c/] ({color:#990000}version{color} {color:#990000}TBD){color} ** [Transcode|http://www.transcoding.org/cgi-bin/transcode] version 1.0.2 or > (optional) ** OpenQuicktime (optional) ** Berkeley MPEG-1 encoder (optional) * *Download and uncompress* the AVED source files that are distributed as tar'ed files, then build the source. The detailed steps to install AVED are: * [AVED Installation - Step 1. Build iLab Saliency Toolkit] * [AVED Installation - Step 2. Build and Install XML Libraries] * [AVED Installation - Step 3. Build and Install Transcode Software (optional)] * [AVED Installation - Step 4. Build and install Berkeley MPEG Encoder (optional)] * [AVED Installation - Step 5. Build Mbarivision]  ]]> 5374267 5407007 export XERCESCROOT= export AVED_BIN=/bin {noformat} Use the following step to build the executable from source: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint} If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ran make. As well make allclean will clean the dependencies file generated from a make. You'll want to do this if you update the source code. {tip}]]> 5374264 5407005 ** [Xerces-C+\+ and perl XML modules|http://xerces.apache.org/xerces-c/] ({color:#990000}version{color} {color:#990000}TBD){color} ** [Transcode|http://www.transcoding.org/cgi-bin/transcode] version 1.0.2 or > (optional) ** OpenQuicktime (optional) ** Berkeley MPEG-1 encoder (optional) * *Download and uncompress* the AVED source files that are distributed as tar'ed files, then build the source. The detailed steps to install AVED are: # [AVED Installation - Step 1. Build iLab Saliency Toolkit] # [AVED Installation - Step 2. Install XML Libraries] # [AVED Installation - Step 3. Build and Install Transcode Software (optional)] # [AVED Installation - Step 4. Build and install Berkeley MPEG Encoder (optional)]  ]]> 5374262 5407006 cd src/xerces runConfigure -p linux gmake sudo gmake install {noformat} {color:#990000}TODO: Verify this - is this for mbarivision ? make sure the Xerces-c library is in your LD_LIBRARY_PATH (export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib){color} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat}]]> 5374263 5407003 ** [Xerces-C+\+ and perl XML modules|http://xerces.apache.org/xerces-c/] ({color:#990000}version{color} {color:#990000}TBD){color} ** [Transcode|http://www.transcoding.org/cgi-bin/transcode] version 1.0.2 or > (optional) ** OpenQuicktime (optional) ** Berkeley MPEG-1 encoder (optional) * *Download and uncompress* the AVED source files that are distributed as tar'ed files, then build the source. The detailed steps to install AVED are: # [AVED Installation - Step 1. Build iLab Saliency Toolkit] # [AVED Installation - Step 2. Install XML Libraries] # [AVED Installation - Step 3. Build and Install Transcode Software (optional)] # [AVED Installation - Step 4. Build and install Berkeley MPEG Encoder (optional)]  ]]> 5374260 5407004 ** [Xerces-C+\+ and perl XML modules|http://xerces.apache.org/xerces-c/] ({color:#990000}version{color} {color:#990000}TBD){color} ** [Transcode|http://www.transcoding.org/cgi-bin/transcode] version 1.0.2 or > (optional) ** OpenQuicktime (optional) ** Berkeley MPEG-1 encoder (optional) * *Download and uncompress* the AVED source files that are distributed as tar'ed files, then build the source. The detailed steps to install AVED are: # [AVED Installation - Step 1. Build iLab Saliency Toolkit] # [AVED Installation - Step 2. Install XML Libraries] # [AVED Installation - Step 3. Build and Install Transcode Software (optional)] # [AVED Installation - Step 4. Build and install Berkeley MPEG Encoder (optional)]  ]]> 5374261 5407016 export XERCESCROOT= {noformat} Use the following step to build the executable from source: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint} If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ran make. As well make allclean will clean the dependencies file generated from a make. You'll want to do this if you update the source code. {tip}]]> 5374273 5407017 export XERCESCROOT= {noformat} Use the following step to build the executable from source: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint} If you update either the Mbarivision or Saliency source code, be sure to run a make allclean. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and, therefore, the dependencies may change so this is required.]]> 5374274 5407012 ./configure make make install {noformat}\\ \\ \\ \\]]> 5374269 5407014 export XERCESCROOT= export AVED_BIN=/bin {noformat} Use the following step to build the executable from source: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint} If you have run make before, you should run a make clean before running make again. This cleans out all the object files that were generated the previous time you ran make. As well make allclean will clean the dependencies file generated from a make. You'll want to do this if you update the source code. {tip}]]> 5374271 5407024 5374281 5407026 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. | | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-clip=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-only-interesting-events \\ | \[yes\] \\ | If saving events, save only the interesting events \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | ]]> 5374283 5407025 {noformat} * Run configure script to setup installation as a submit and execute only node {noformat} /opt/condor-xxxxxx/condor_configure --type=submit,execute,manager --owner=user --install-dir=/opt/condor-xxxxx {noformat} {info:title=}Make sure in /opt/condor-xxxxxx/etc/condor_config line reads: DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD {info} h3.     Installing Condor as a service on Linux * Create condor.sh file in /etc/profile.d then add the following to it: {noformat} CONDOR_ROOT=/opt/condor-xxxxxxxxxxx export PATH=$PATH:$CONDOR_ROOT/sbin:$CONDOR_ROOT/bin export CONDOR_CONFIG=$CONDOR_ROOT/etc/condor_config {noformat} * Install condor service script to execute condor on bootup {noformat} cd /opt/condor-xxxxxx/etc/examples cp condor.boot /etc/init.d/condor {noformat} * Edit condor service script replacing MASTER line {noformat} MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add . /etc/profile.d/condor.sh *before* the line MASTER {noformat} . /etc/profile.d/condor.sh MASTER=$CONDOR_ROOT/sbin/condor_master {noformat} * Add soft links to the condor startup script {noformat} ln -s /etc/init.d/condor /etc/rc2.d/S100condor ln -s /etc/init.d/condor /etc/rc2.d/K100condor {noformat} * Start the condor service {noformat} service condor start {noformat} h3.     Configuring Condor Change the following value in the /opt/condor-xxxxxxx/local.xxxxxx/condor_config.local\\ {noformat} ## When is this machine willing to start a job? START = TRUE ## When to suspend a job? SUSPEND = FALSE ## When to nicely stop a job? ## (as opposed to killing it instantaneously) PREEMPT = FALSE ## When to instantaneously kill a preempting job ## (e.g. if a job is in the pre-empting stage for too long) KILL = FALSE {noformat}\\ \\ \\ \\ \\ \\ h1. Installing AVED as a web-service A web-service has been written to make the system easy to interface and automate. AVED web-service requires AVED and its dependencies to be install (cf. AVED Guide section Installation) and requires Condor as well (cf. AVED Guide section Special Features-Installing an AVED-enabled Condor node). Moreover, in order to deploy AVED web-service, a web application server is required. We'll consider in this Guide starting from scratch, so if you already have an application server runing and install go to section: Deploy the AVED web-service. \\ The AVED web-service is distributed as source files that you must compile yourself, however, a ant script is provided to help you in this step. Here is a short overview of the steps to build and deploy the AVED web \-service from sources: \\ * *Preparation:* AVED web-services required a web server and ant to be built. See Installing AVED as a web-service - Preparation section for more information. * *Download* the AVED source files (distributed as tar'ed and compressed files). Place the file in a place of your own choice. * *Untar and uncompress{*}the file to the place you want the program installed. You will then need to read the next section about how to configure before you compile the program. Below is shown the exact commands: tar \-xzvf /path/to/aved-web-service-1.0.0.tar.gz * Now change to the new directory cd aved-webservice * Run ant. ant * copy and paste the build/AvedWebService.aar files into the /webapps/axis2/WEB-INF/services cp build/AvedWebService.aar /webapps/axis2/WEB-INF/services * copy and paste the jars needed by the web service from the jars folder into the /webapps/axis2/WEB-INF/lib cp jars/*.jar /webapps/axis2/WEB-INF/lib * restart your web server application \\ h3.     Preparation for deploy the AVED web-service In this section we're gonna install the application server apache Tomcat, the web-service utils with apach Axis2, and finally ant to be able to built the AVED web-service. If you already have an application web-server install and runing you can directly go to the Deploy the AVED web-service. h5.              Installing Java Apache Tomcat and ant require Java to be install on your computer. You can process different way: RPMs, self-extracted, or sources. If you're using sources, download the binaries distribution from [http://www.sun.com/java/]. Then untat and set the JAVA_HOME environmental variable to the full path of your Java distribution. {noformat} tar xzvf jdkx.xxx.tar.gz export JAVA_HOME= {noformat} h5.             Installing apache Tomcat To install Apache tomcat, first download it from [http://tomcat.apache.org/] (download the core version). Then extract it into the folder where you want to setup your application server. \\ {noformat} tar xzvf apache-tomcat-xxxxxx.tar.gz {noformat} To test if your application server is on, just start it, you have to be in the apache-tomcat folder: {noformat} ./bin/catalina.sh start {noformat} Start your favorite browser and tape: [http://localhost:8080/], if everything is working you should fall on the apache-tomcat presentation page. Now your application server is up, download the web-service utilities from [http://ws.apache.org/axis2/] (download the war distribution) and copy it into the /webapps folder. {noformat} cp /axis2.war /webapps {noformat} Then on your browser, tape: [http://localhost:8080/axis2]. You should find at this URL the axis2 presentation page. \\ \\ h5.             Installing apache Ant The binarie distribution can be found at: [http://ant.apache.org/bindownload.cgi]. Download it and untar it into the folder you want ant to be install. You can install it from rpms as well. Ant is not required to build the AVED web-service, it's just more convinient to build it, but you can compile it by yourself using javac. Don't forget to add to the classpath the jars included into the aved-webservice/jars folder. \\ {noformat} tar xzvf apache-antxxxxxxx.tar.gz {noformat} h5.             Allowing condor to be requested from http Open the file /etc/condor_config and add the following lines (wherever in part 1) {noformat} SCHEDD_ARGS=-p 8181 ENABLE_SOAP = TRUE ALLOW_SOAP = */* ENABLE_WEB_SERVER = TRUE QUEUE_ALL_USERS_TRUSTED = TRUE {noformat}  You can set the SCHEDD_ARGS to the port you prefere, here we choose 8181. You have to restart condor or juste reconfig it: \\ {noformat} condor_reconfig {noformat}\\ \\ \\ h3.     Deploy the AVED web-service To deploy the AVED web-service, ant and an application web-server are required, if you don't have any please refer to AVED Guide - Special Features section Installing AVED as a web-service - Preparation for deploy the AVED web-service. \\ The web service provided condains the service (src/org/mbari/aved/webservice/server/AvedService.java) and an exemple to request it (src/org/mbari/aved/webservice/client/AvedClient.java). Before deploying the web-service, you have to edit the java code in order to provide the user Condor is gonna run with and the computer sets. For that edit the file AvedService.java in src/org/mbari/aved/webservice/server {noformat} public static String SCHEDD_LOCATION = "http://host.domain.name.org:8181"; public static String USER = "aved"; {noformat} Then, compile the source by tapping {noformat} ant {noformat} If everything is going well, you should see a BUILD SUCCESSFULL printed, and a build folder should have been created. In these folder you'll find a AvedService.aar file what is the web-service \! To deploy it, just copy and past this file into your application server directory, and the jars from the jars into the application server lib directory: {noformat} cp build/AvedService.aar /webapps/axis2/WEB-INF/services/ cp jars/*.jar /webapps/axis2/WEB-INF/lib/ {noformat} Restart tomcat, and check with your browser if your web-service is up by tapping [http://host:8080/axis2/services/listServices], AvedService should be listed. The AVED web-service requires 4 envirenmental variables: {noformat} export MBARIVISIONROOT= export JAVA_HOME= export CONDOR_CONFIG=/opt/condor-xxxxxxxxx/etc/condor_config export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} You can know test it with the client code provided \! \\ The web service is composed of 3 functions:             - OMElement sendJobToAved (String path): this function takes for parameter the path of the video to be processed and return an XML file with node1=the cluster number and node2=the job number             - OMElement getJobStatus (int cluster, int job): this function takes the cluster number and the job number and return the job status (1: Idle, 2:Running, 3:Removed, 4:Completed, 5:Held).             - OMElement getResult (int cluster, int job): this function takes the cluster number and the job number and return the XML result of the processing. The web service client is basicly a java code what send a job to AVED wait until the status id is at 4 (completed) and get the result. \\ \\ h3.     Installing the AVED web-service as a service on Linux * Create tomcat.sh file in /etc/profile.d then add the following to it: {noformat} export JAVA_HOME= export MBARIVISIONROOT= export CONDOR_SPOOL=/opt/condor-xxxxxxx/local.xxxxxxx/spool {noformat} * Create tomcat file in /etc/init.d then add the following to it: {noformat} . /etc/profile.d/tomcat.sh /bin/catalina.sh start {noformat} \* Add soft links to the tomcat startup script {noformat} ln -s /etc/init.d/tomcat /etc/rc2.d/S100tomcat ln -s /etc/init.d/tomcat /etc/rc2.d/K100tomcat {noformat} Start the tomcat service \\ {noformat} service tomcat start {noformat}\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 5374282 5407019 export XERCESCROOT= {noformat} Use the following step to build the executable from source: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a make allclean. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and, therefore, the dependencies may change so this is required. {tip}]]> 5374276 5407022 5374279 5407021 5374278 5407031 5374288 5407032 5374289 5407029 5374286 961 964 960 963 5407053 5374313 11829912 11797163 5407055 5374315 5407062 5374323 5407065 export XERCESCROOT= {noformat} Use the following step to build the executable from source: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a cleaner build. {tip}]]> 5374326 5407064 5374325 5407070 export XERCESCROOT= {noformat} Use the following step to build the executable from source: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a cleaner build. {tip} h2. Installing AVED Scripts Scripts are located in the scripts directory. There is a simple install script that will install them to the /usr/local/aved/scripts directory and setup your user paths called *install*. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 5374331 5407067 export XERCESCROOT= {noformat} Use the following step to build the executable from source: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a cleaner build. {tip}]]> 5374328 5407072 export XERCESCROOT= {noformat} Use the following step to build the executable from source: {noformat} cd ./configure make make install {noformat} {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a cleaner build. {tip} h2. Installing AVED Scripts Scripts are located in the scripts directory. There is a simple install script that will install them to the /usr/local/aved/scripts directory and setup your user paths called *install*. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 5374333 927 930 11829947 11797198 11829945 11797196 5407086 Administration->Network, and change accordingly. h3.  Test Programs  Two types of example scripts have been \\]]> 5374347 11829943 11797194 11829944 11797195 5407088 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  AVED was installed as the user root. An additional account was setup for a user aved. Passwords for both have been delivered to Dhugal. h3. JAMSTEC Video Data and Locations Three sets of test video data are on this laptop.  All of this video is JAMSTEC video send to us and I believe all of it is high-definition size of 1920x1080. || Directory || Type || | /home/aved/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording.  Frames were extracted from a HD tape.\\ | | /home/aved/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording.  Frames were extracted from a HD tape. | | /home/aved/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a PICASSO slow moving midwater video recording.  Frames were extracted from a HD tape. | \\ benthic and midwater    \\]]> 5374349 11829942 11797193 5407090 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  AVED was installed as the user root. An additional account was setup for a user aved. Passwords for both have been delivered to Dhugal. h3. JAMSTEC Video Data and Locations Three sets of test video data are on this laptop and I believe all of it is high-definition size of 1920x1080.  Some are stills, and one is a video clip.  All of this data was provided by JAMSTEC either on  tape, or digitally. || Directory || Type || | /home/aved/Desktop/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording.  Frames were extracted from a HD tape. \\ | | /home/aved/Desktop/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording.  Frames were extracted from a HD tape. | | /home/aved/Desktop/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a PICASSO slow moving midwater video recording.  Frames were extracted from a HD tape. | | /home/aved/Video/midwater/midwater/midwater_slowtransect | |]]> 5374351 11829940 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now, go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|mbarivision Installation - Step 2. Build and Install XML Libraries]]]> 11797191 11829938 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now, go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|mbarivision Installation - Step 2. Build and Install XML Libraries]]]> 11797189 11829936 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now, go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|mbarivision Installation - Step 2. Build and Install XML Libraries]]]> 11797187 11829934 11797185 11829932 11797183 5407100 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  AVED was installed as the user root. An additional account was setup for a user aved. Passwords for both have been delivered to Dhugal. h3. JAMSTEC Video Data and Locations Three sets of test video data are on this laptop and I believe all of it is high-definition size of 1920x1080.  Some are still pictures, and one is a video clip.  All of this data was provided by JAMSTEC either on  tape, or digitally. || Directory || Type || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a PICASSO benthic video recording.  Frames were extracted from a HD tape. \\ | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a PICASSO fast moving midwater video recording.  Frames were extracted from a HD tape. | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a PICASSO slow moving midwater video recording.  Frames were extracted from a HD tape. | | /home/aved/Video/20080604T063139.mov | Quicktime movie encoded with mpeg4 codec. \\ |]]> 5374362 11829928 11797179 902 905 903 906 5407103 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  AVED was installed as the user root. An additional account was setup for a user aved. Passwords for both have been delivered to Dhugal. h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Some are still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided, in addition to the AVED scripts, to give examples of how to process the data.  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type\\ || Process Command || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a \\ PICASSO benthic video recording. \\ Frames were extracted from HD tape. | {code} cd /home/aved/Pictures/benthic/benthic_ajamstec_runmbarivis or jamstec_runmbarivis_displayalg {code} | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a \\ PICASSO fast moving midwater video recording.  \\ Frames were extracted from a HD tape. | {code} cd /home/aved/Pictures/midwater/midwater/midwater_fasttransectjamstec_runmbarivis or jamstec_runmbarivis_displayalg {code} | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording.  \\ Frames were extracted from a HD tape. | | | /home/aved/Video/20080604T063139.mov | Quicktime movie encoded with mpeg4 codec.  \\ This was was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] \\ date and time convention because this is used by AVED scripts to timestamp events. \\ E.g. assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. \\ | | h3. JAMSTEC Custom Scripts || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a.\\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages and runs the mbarivis_command. Also rescales the input to 640x480 to make the display more manageable. \\ | | \\ | | \\]]> 5374364 11829926 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now, go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|mbarivision Installation - Step 2. Build and Install XML Libraries]]]> 11797177 904 907 11829925 ./configure --enable-shared --prefix=/usr make make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like \--prefix, \--enable-quitecompile, etc. but don't remove the options above. If you want to experiment with the saliency toolkit, copy it to a separate directory that won't be used in the AVED mbarivision build \! {warning} Now, go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|mbarivision Installation - Step 2. Build and Install XML Libraries]]]> 11797176 5407105 Administration->Network, and change accordingly. h3. AVED Installation AVED was installed according to the instructions [AVED Installation].  AVED was installed as the user root. An additional account was setup for a user aved. Passwords for both have been delivered to Dhugal. h3. JAMSTEC Video Data Locations and Processing Scripts Three sets of test high-definition video data were installed on this laptop.  Some are still pictures, and one is a video clip.  All of this data was provided by JAMSTEC on  tape, or digitally. Some basic scripts were provided, in addition to the AVED scripts, to give examples of how to process the data.  For more information on running AVED, please see the [AVED Running Howto] guide. || Directory || Data Type \\ || Process Command \\ || | /home/aved/Pictures/benthic/benthic_a | Individual ppm frames from (I think) a \\ PICASSO benthic video recording. \\ Frames were extracted from HD tape. | {code} cd /home/aved/Pictures/benthic/benthic_a jamstec_runmbarivis or jamstec_runmbarivis_displayalg {code} | | /home/aved/Pictures/midwater/midwater/midwater_fasttransect | Individual ppm frames from (I think) a \\ PICASSO fast moving midwater video recording.  \\ Frames were extracted from a HD tape. | {code} cd /home/aved/Pictures/midwater/midwater/midwater_fasttransect jamstec_runmbarivis or jamstec_runmbarivis_displayalg {code} | | /home/aved/Pictures/midwater/midwater/midwater_slowtransect | Individual ppm frames from (I think) a \\ PICASSO slow moving midwater video recording.  \\ Frames were extracted from a HD tape. | | | /home/aved/Video/20080604T063139.mov | Quicktime movie encoded with mpeg4 codec.  \\ This was was named according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601] \\ date and time convention because this is used by AVED scripts to timestamp events. \\ E.g. assumes the tape recording started on 06/06/2008 at 06:31:39 UTC. | | \\ \\ | \\ | \\ | | \\ | \\ | h3. JAMSTEC Custom Scripts || Script || Description || | /home/aved/jamstec_runmbarivis | Simple script that clears the MBARIVISION_OPTIONS variable and runs the mbarivis_command script. Nothing special here - just a wrapper script.  Use this to process the benthic_a or midwater_fast/slowtransect images. This must be executed in the root directory of the ppm frames, e.g. /home/aved/Pictures/benthic/benthic_a. \\ | | /home/aved/jamstec_runmbarivis_displayalg | Simple script that sets the mbarivision options  to display the AVED algorithm output at various stages and runs the mbarivis_command. Also rescales the input to 640x480 to make the display more manageable. \\ | | \\ | | \\]]> 5374366 12550268 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. { ]]> 12484733 12550269 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. { ]]> 12484734 12550264 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *mvn clean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 12484729 12550266 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *mvn clean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 12484731 12550260 12484725 12550261 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *mvn clean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 12484726 12550255 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *mvn clean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 12484720 12550258 12484723 12550251 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The install goes into defined in the parent pom.xml properties. Make sure you have the appropriate permissions to write to the directory. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *mvn clean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 12484716 12550253 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The install goes into defined in the parent pom.xml properties. Make sure you have the appropriate permissions to write to the directory. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *mvn clean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 12484718 12550247 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The install goes into defined in the parent pom.xml properties. Make sure you have the appropriate permissions to write to the directory. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *mvn clean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 12484712 12550248 12484713 12550249 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The install goes into defined in the parent pom.xml properties. Make sure you have the appropriate permissions to write to the directory. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *mvn clean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 12484714 12550243 $\{HOME\}/aved $\{HOME\}/aved/Xerces-2_7_0 $\{HOME\}/aved/saliency These paths must define the base locations of the installed [saliency|mbarivision Installation - Step 1. Build iLab Saliency Toolkit] and [xerces|mbarivision Installation - Step 2. Build and Install XML Libraries] code. To build the mbarivision executable: {noformat} cd mvn compile install {noformat} The install goes into {{}. Make sure you have the appropriate permissions to write to the directory. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *mvn clean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 12484708 12550245 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} These paths must define the base locations of the installed [saliency|mbarivision Installation - Step 1. Build iLab Saliency Toolkit] and [xerces|mbarivision Installation - Step 2. Build and Install XML Libraries] code. To build the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build the pmbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The install goes into defined in the parent pom.xml properties. Make sure you have the appropriate permissions to write to the directory. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *mvn clean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 12484710 12550241 12484706 12550240 ./configure --with-saliency-root= make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 12484705 12550238 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default but you can change the install path with the {{\--prefix}} argument to {{configure}}. {tip:title=Handy Hint}If you update either the mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. {tip} ]]> 12484703 10945026 10912271 10944962 10912207 12550157 export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} {tip:title=Handy Hint} If you installed the Xerces C+\+ library to a non-standard library location, be sure to add to the loader path in /etc/ld.so.conf the location, and run ldconfig -v to refresh the loader. {tip} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|mbarivision Installation - Step 6. Build and Install mbarivision or pmbarivision], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|mbarivision Installation - Step 3. Build and Install Transcode].]]> 12484621 12255259 12222491 12255266 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. *It is important to format the filenames with a single dot '.' e.g. a filename formatted like T.f00000.ppm isn't supported, but Tf00000.ppm is okay, in this case you would pass the in argument with Tf#.ppm.*| | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-num=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-non-interesting-events \\ | \[yes\] \\ | If saving events, save non interesting events in addition to interesting event. Default is to not save non interesting events. \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \-mbari-mosaic-benthic-stills | \[no\] | Implements good choice of options to experiment with processing still images from a still or moving camera traversing the sea bottom. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --mbari-cache-size=2 --mbari-max-WTA-points=15 --mbari-max-evolve-msec=15000 --vc-type=OIC --use-random=false --test-mode=true --oricomp-type=Steerable --mbari-cache-size=2 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-benthic-video | \[no\] | Implements good choice of options to experiment with processing video from a moving camera traversing the sea bottom. EQUIVALENT TO: --mbari-saliency-dist=5 --mbari-tracking-mode=NearestNeighbor --mbari-saliency-input-image=DiffMean --mbari-segment-algorithm-input-image=MaxRGB --vc-type=O:5IC --use-random=false --test-mode=true --ori-interaction=None --oricomp-type=Steerable --mbari-cache-size=15 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-midwater-video | \[no\] | Implements good choice of options to experiment with processing video from a moving camera traversing the midwater sea column. EQUIVALENT TO: --mbari-saliency-dist=5 --mbari-tracking-mode=KalmanFilter --mbari-saliency-input-image=DiffMean --mbari-segment-algorithm-input-image=MaxRGB --vc-type=O:5IC --use-random=false --test-mode=true --mbari-cache-size=10 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-mosaic-stills | \[no\] | Implements good choice of options to experiment with still frames collected from a moving camera in mosaic form. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --boring-sm-mv=0.25 --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --vc-type=Variance --use-random=false --mbari-saliency-input-image=Raw --mbari-cache-size=2 --mbari-max-WTA-points=25 --mbari-max-evolve-msec=15000 \\ | | \-mbari-timelapse-stills | \[no\] | Implements good choice of options to experiment with still frames collected from a stationary time-lapse camera. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=NearestNeighbor --mbari-keep-boring-WTA-points=yes --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --mbari-cache-size=10 --qtime-decay=1.0 --vc-type=Variance --use-random=false --mbari-max-WTA-points=30 --mbari-max-evolve-msec=15000 --use-random=false --use-older-version=false \\ | | \-mbari-timelapse-rover-stills | \[no\] | Implements good choice of options to experiment with time-lapse still frames collected from a benthic moving camera . EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --qtime-decay=1.0 --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --vc-type=O:5IC --use-random=false --mbari-max-WTA-points=15 --mbari-max-evolve-msec=15000 \\ | | \--mbari-max-WTA-points= | \[20\] | Maximum number of winner-take-all points to find in each frame \\ | | \--mbari-max-evolve-msec= | \[500\] | Maximum amount of time in milliseconds to evolve the brain until stopping \\ | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average. \\ | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Tracking mode used to track events between frames \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-segment-algorithm-input-image= | \[MaxRGB\] \\ | Segment algorithm input images type \\ | | \--mbari-segment-algorithm-se-type= | \[benthic\] \\ | Jerome Mariette's segmentation algorithm structure element test \\ | | \--mbari-segment-input-image= | \[DiffMean\] \\ | Saliency input image type \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image. *Important* this only masks the area to look for detections - it does not mask the area from the saliency computation. \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | | \--mbari-saliency-dist= \\ | \[5\] \\ | The number of frames to delay between saliency map computations Reduce this to improve your detection rate. Warning reducing this *will* increase your computation time. \\ |]]> 12222498 12255254 12222486 12255252 12222484 12255257 12222489 12255255 12222487 12255256 12222488 12255246 12222478 12255250 12222482 12255248 12222480 12255247 12222479 12255240 12222472 12255291 12222523 15237135 15204367 12255284 12222516 12255286 12222518 12255287 export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} {tip:title=Handy Hint} If you installed the Xerces C+\+ library to a non-standard library location, be sure to add to the loader path in /etc/ld.so.conf the location, and run ldconfig -v to refresh the loader. {tip} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|mbarivision Installation - Step 6. Build and Install mbarivision or pmbarivision], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|mbarivision Installation - Step 3. Build and Install Transcode and mpeg4ip Software].]]> 12222519 12255288 ./configure make sudo make install {noformat} h1. About OpenQuicktime  Early in the AVED development we put our video into Quicktime containers and added a timecode track that corresponded to the time track recorded on our tapes. The SMPTE 12M standard is used in video and in film for specifying time. This is what comes off our tape-decks and what was added to the Quicktime timecode track. See for more information: [http://en.wikipedia.org/wiki/SMPTE_time_code]. We did this by modifying the Linux OpenQuicktime library to support reading and writing a single timecode track. We no longer support OpenQuicktime, but include it here for backwards support of our older digitized video. We now maintain the time code throughout our processing by naming the video according to the [ISO8601|http://en.wikipedia.org/wiki/ISO_8601]standard, and then maintain the timecode track in the xml formatted results of the output. This allows us more flexibility in supporting different video containers, and since support for OpenQuicktime is diminishing, abandoning it was a sensible step. h3. Building and Installing OpenQuicktime The custom version of OpenQuicktime that includes the ability to write and read a single timecode track can be found on our internal CVS server Moonjelly. CVS check out the aved/OpenQuicktime module, build, then install.  The following instructions assume you have access to, and know how to check-out code from the internal MBARI CVS server Moonjelly. If you don't, then see these instructions for more information: [welcome to CVS|https://oceana.mbari.org/confluence/display/CLT/Welcome+to+CVS%21]. First check-out the module:  {noformat} cvs co aved/OpenQuicktime {noformat} Then build according to the following: \\ {noformat} cd ./configure make sudo make install {noformat} When you are done, you can skip to [step 6|mbarivision Installation - Step 6. Build and Install mbarivision or pmbarivision], or continue to the next optional step [AVED Installation - Step 5. Build and install Berkeley MPEG Encoder|mbarivision Installation - Step 5. Build and install Berkeley MPEG Encoder (optional)]\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\]]> 12222520 12255289 12222521 12255290 12222522 12255268 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. *It is important to format the filenames with a single dot '.' e.g. a filename formatted like T.f00000.ppm isn't supported, but Tf00000.ppm is okay, in this case you would pass the in argument with Tf#.ppm.*| | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-num=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-non-interesting-events \\ | \[yes\] \\ | If saving events, save non interesting events in addition to interesting event. Default is to not save non interesting events. \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \-mbari-mosaic-benthic-stills | \[no\] | Implements good choice of options to experiment with processing still images from a still or moving camera traversing the sea bottom. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --mbari-cache-size=2 --mbari-max-WTA-points=15 --mbari-max-evolve-msec=15000 --vc-type=OIC --use-random=false --test-mode=true --oricomp-type=Steerable --mbari-cache-size=2 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-benthic-video | \[no\] | Implements good choice of options to experiment with processing video from a moving camera traversing the sea bottom. EQUIVALENT TO: --mbari-saliency-dist=5 --mbari-tracking-mode=NearestNeighbor --mbari-saliency-input-image=DiffMean --mbari-segment-algorithm-input-image=MaxRGB --vc-type=O:5IC --use-random=false --test-mode=true --ori-interaction=None --oricomp-type=Steerable --mbari-cache-size=15 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-midwater-video | \[no\] | Implements good choice of options to experiment with processing video from a moving camera traversing the midwater sea column. EQUIVALENT TO: --mbari-saliency-dist=5 --mbari-tracking-mode=KalmanFilter --mbari-saliency-input-image=DiffMean --mbari-segment-algorithm-input-image=MaxRGB --vc-type=O:5IC --use-random=false --test-mode=true --mbari-cache-size=10 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-mosaic-stills | \[no\] | Implements good choice of options to experiment with still frames collected from a moving camera in mosaic form. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --boring-sm-mv=0.25 --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --vc-type=Variance --use-random=false --mbari-saliency-input-image=Raw --mbari-cache-size=2 --mbari-max-WTA-points=25 --mbari-max-evolve-msec=15000 \\ | | \-mbari-timelapse-stills | \[no\] | Implements good choice of options to experiment with still frames collected from a stationary time-lapse camera. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=NearestNeighbor --mbari-keep-boring-WTA-points=yes --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --mbari-cache-size=10 --qtime-decay=1.0 --vc-type=Variance --use-random=false --mbari-max-WTA-points=30 --mbari-max-evolve-msec=15000 --use-random=false --use-older-version=false \\ | | \-mbari-timelapse-rover-stills | \[no\] | Implements good choice of options to experiment with time-lapse still frames collected from a benthic moving camera . EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --qtime-decay=1.0 --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --vc-type=O:5IC --use-random=false --mbari-max-WTA-points=15 --mbari-max-evolve-msec=15000 \\ | | \--mbari-max-WTA-points= | \[20\] | Maximum number of winner-take-all points to find in each frame \\ | | \--mbari-max-evolve-msec= | \[500\] | Maximum amount of time in milliseconds to evolve the brain until stopping \\ | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average. \\ | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Tracking mode used to track events between frames \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-segment-algorithm-input-image= | \[MaxRGB\] \\ | Segment algorithm input images type \\ | | \--mbari-segment-algorithm-se-type= | \[benthic\] \\ | Jerome Mariette's segmentation algorithm structure element test \\ | | \--mbari-segment-input-image= | \[DiffMean\] \\ | Saliency input image type \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image. *Important* this only masks the area to look for detections - it does not mask the area from the saliency computation. \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | | \--mbari-min-event-frames= | \[1\] \\ | The minimum number of frames an event must be to be candidate \\ | | \--mbari-max-event-frames= \\ | \[-1\] \\ | The maximum number of frames an event can be, to be candidate. Defaults to infinite \\ | | \--mbari-saliency-dist= \\ | \[5\] \\ | The number of frames to delay between saliency map computations Reduce this to improve your detection rate. Warning reducing this *will* increase your computation time. \\ |]]> 12222500 10944783 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. *It is important to format the filenames with a single dot '.' e.g. a filename formatted like T.f00000.ppm isn't supported, but Tf00000.ppm is okay, in this case you would pass the in argument with Tf#.ppm.*| | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-num=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-non-interesting-events \\ | \[yes\] \\ | If saving events, save non interesting events in addition to interesting event. Default is to not save non interesting events. \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \-mbari-mosaic-benthic-stills | \[no\] | Implements good choice of options to experiment with processing still images from a still or moving camera traversing the sea bottom. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --mbari-cache-size=2 --mbari-max-WTA-points=15 --mbari-max-evolve-msec=15000 --vc-type=OIC --use-random=false --test-mode=true --oricomp-type=Steerable --mbari-cache-size=2 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-benthic-video | \[no\] | Implements good choice of options to experiment with processing video from a moving camera traversing the sea bottom. EQUIVALENT TO: --mbari-saliency-dist=5 --mbari-tracking-mode=NearestNeighbor --mbari-saliency-input-image=DiffMean --mbari-segment-algorithm-input-image=MaxRGB --vc-type=O:5IC --use-random=false --test-mode=true --ori-interaction=None --oricomp-type=Steerable --mbari-cache-size=15 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-midwater-video | \[no\] | Implements good choice of options to experiment with processing video from a moving camera traversing the midwater sea column. EQUIVALENT TO: --mbari-saliency-dist=5 --mbari-tracking-mode=KalmanFilter --mbari-saliency-input-image=DiffMean --mbari-segment-algorithm-input-image=MaxRGB --vc-type=O:5IC --use-random=false --test-mode=true --mbari-cache-size=10 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-mosaic-stills | \[no\] | Implements good choice of options to experiment with still frames collected from a moving camera in mosaic form. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --boring-sm-mv=0.25 --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --vc-type=Variance --use-random=false --mbari-saliency-input-image=Raw --mbari-cache-size=2 --mbari-max-WTA-points=25 --mbari-max-evolve-msec=15000 \\ | | \-mbari-timelapse-stills | \[no\] | Implements good choice of options to experiment with still frames collected from a stationary time-lapse camera. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=NearestNeighbor --mbari-keep-boring-WTA-points=yes --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --mbari-cache-size=10 --qtime-decay=1.0 --vc-type=Variance --use-random=false --mbari-max-WTA-points=30 --mbari-max-evolve-msec=15000 --use-random=false --use-older-version=false \\ | | \-mbari-timelapse-rover-stills | \[no\] | Implements good choice of options to experiment with time-lapse still frames collected from a benthic moving camera . EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --qtime-decay=1.0 --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --vc-type=O:5IC --use-random=false --mbari-max-WTA-points=15 --mbari-max-evolve-msec=15000 \\ | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average. \\ | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image. *Important* this only masks the area to look for detections - it does not mask the area from the saliency computation. \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | | \--mbari-saliency-dist= \\ | \[5\] \\ | The number of frames to delay between saliency map computations. Reduce this to improve your detection rate. Warning reducing this *will* increase your computation time. \\ |]]> 10912021 12550294 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. { ]]> 12484759 12550291 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. { ]]> 12484756 12550292 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. { ]]> 12484757 12550298 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. ]]> 12484763 12550295 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. ]]> 12484760 12550296 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. ]]> 12484761 12550301 ... ${HOME}/aved ${HOME}/Xerces-2_7_0 ${HOME}/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. ]]> 12484766 12550299 ... ${HOME}/aved ${HOME}/Xerces-2_7_0 ${HOME}/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. ]]> 12484764 10944821 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. *It is important to format the filenames with a single dot '.' e.g. a filename formatted like T.f00000.ppm isn't supported, but Tf00000.ppm is okay, in this case you would pass the in argument with Tf#.ppm.*| | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-num=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-non-interesting-events \\ | \[yes\] \\ | If saving events, save non interesting events in addition to interesting event. Default is to not save non interesting events. \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \-mbari-mosaic-benthic-stills | \[no\] | Implements good choice of options to experiment with processing still images from a still or moving camera traversing the sea bottom. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --mbari-cache-size=2 --mbari-max-WTA-points=15 --mbari-max-evolve-msec=15000 --vc-type=OIC --use-random=false --test-mode=true --oricomp-type=Steerable --mbari-cache-size=2 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-benthic-video | \[no\] | Implements good choice of options to experiment with processing video from a moving camera traversing the sea bottom. EQUIVALENT TO: --mbari-saliency-dist=5 --mbari-tracking-mode=NearestNeighbor --mbari-saliency-input-image=DiffMean --mbari-segment-algorithm-input-image=MaxRGB --vc-type=O:5IC --use-random=false --test-mode=true --ori-interaction=None --oricomp-type=Steerable --mbari-cache-size=15 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-midwater-video | \[no\] | Implements good choice of options to experiment with processing video from a moving camera traversing the midwater sea column. EQUIVALENT TO: --mbari-saliency-dist=5 --mbari-tracking-mode=KalmanFilter --mbari-saliency-input-image=DiffMean --mbari-segment-algorithm-input-image=MaxRGB --vc-type=O:5IC --use-random=false --test-mode=true --mbari-cache-size=10 --use-random=false --use-older-version=false --shape-estim-mode=ConspicuityMap --ior-type=ShapeEst \\ | | \-mbari-mosaic-stills | \[no\] | Implements good choice of options to experiment with still frames collected from a moving camera in mosaic form. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --boring-sm-mv=0.25 --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --vc-type=Variance --use-random=false --mbari-saliency-input-image=Raw --mbari-cache-size=2 --mbari-max-WTA-points=25 --mbari-max-evolve-msec=15000 \\ | | \-mbari-timelapse-stills | \[no\] | Implements good choice of options to experiment with still frames collected from a stationary time-lapse camera. EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=NearestNeighbor --mbari-keep-boring-WTA-points=yes --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --mbari-cache-size=10 --qtime-decay=1.0 --vc-type=Variance --use-random=false --mbari-max-WTA-points=30 --mbari-max-evolve-msec=15000 --use-random=false --use-older-version=false \\ | | \-mbari-timelapse-rover-stills | \[no\] | Implements good choice of options to experiment with time-lapse still frames collected from a benthic moving camera . EQUIVALENT TO: --mbari-saliency-dist=1 --mbari-tracking-mode=None --mbari-keep-boring-WTA-points=yes --qtime-decay=1.0 --mbari-save-non-interesting-events=yes --mbari-segment-algorithm-input-image=MaxRGB --mbari-saliency-input-image=Raw --vc-type=O:5IC --use-random=false --mbari-max-WTA-points=15 --mbari-max-evolve-msec=15000 \\ | | \--mbari-max-WTA-points= | \[20\] | Maximum number of winner-take-all points to find in each frame \\ | | \--mbari-max-evolve-msec= | \[500\] | Maximum amount of time in milliseconds to evolve the brain until stopping \\ | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average. \\ | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-segment-algorithm-input-image= | \[MaxRGB\] \\ | Segment algorithm input images type \\ | | \--mbari-segment-algorithm-se-type= | \[benthic\] \\ | Jerome Mariette's segmentation algorithm structure element test \\ | | \--mbari-segment-input-image= | \[DiffMean\] \\ | Saliency input image type \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image. *Important* this only masks the area to look for detections - it does not mask the area from the saliency computation. \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | | \--mbari-saliency-dist= \\ | \[5\] \\ | The number of frames to delay between saliency map computations Reduce this to improve your detection rate. Warning reducing this *will* increase your computation time. \\ |]]> 10912062 12550278 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. { ]]> 12484743 12550276 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. { ]]> 12484741 12550282 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. { ]]> 12484747 12550280 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. { ]]> 12484745 12550285 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. { ]]> 12484750 12550283 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. { ]]> 12484748 12550289 ... ${HOME}/aved ${HOME}/aved/Xerces-2_7_0 ${HOME}/aved/saliency {code} To build and install the mbarivision executable: {noformat} mvn reactor:make -Dmake.folders=aved-mbarivision {noformat} To build and install the pmbarivision and pvisionTCPmbari executables: {noformat} mvn reactor:make -Dmake.folders=aved-pmbarivision {noformat} The binaries will be installed to the directory defined by the property in the parent pom.xml. Make sure you have the appropriate permissions to write to the directory. { ]]> 12484754 10387839 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like --prefix, --enable-quitecompile, etc. but don't remove the options above. If you want to tinker with the saliency toolkit, copy it to a separate directory that you won't use in the AVED mbarivision build ! {warning} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 10355102 10387841 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like --prefix, --enable-quitecompile, etc. but don't remove the options above. If you want to tinker with the saliency toolkit, copy it to a separate directory that you won't use in the AVED mbarivision build ! {warning} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 10355104 10387842 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like --prefix, --enable-quitecompile, etc. but don't remove the options above. If you want to tinker with the saliency toolkit, copy it to a separate directory that you won't use in the AVED mbarivision build ! {warning} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 10355105 10944748 x | \[0x0\] \\ | Rescale input frames to fixed dims, or 0x0 for no rescaling | | \--\[no\]preserve-input-aspect \\ | \[no\] \\ | Preserve input frame aspect ratio if rescaling to fixed dims \\ | | \--zero-number-frames= | \[false\] \\ | Force all input and output frames to have the number 000000 | | \--in=<\[type\]:\[spec\]> | required | Reads input from one or more raster files. The leading 'raster:' may be omitted if the file has one of the known raster extensions: .pnm, .pgm, .ppm, .pbm, .pfm, .png, .jpeg, .jpg, .rgb555, .rgb565, .rgb24, .rgb32, .yuyv, .uyvy, .yuv444, .yuv422, .yuv411, .yuv420, .yuv410, .yuv444p, .yuv422p, .yuv411p, .yuv420p, .yuv410p; or, any of the above with an additional .gz or .bz2 extension, in which case the image file will be transparently decompressed. If the given filename includes a pair of hashes ('#'), then characters in between the hashes will be interpreted as a minimum numeric field width, and the frame number will be formatted as a zero-padded string to that minimum width, and will be substituted for the entire #nnn# sequence. As special cases, a single '#' is equivalent to '#6#', and '##' is equivalent to '#0#'. Thus a filename of foo#.png or foo#6#.png will cause the stream to read foo000000.png, foo000001.png, etc.; foo##.png or foo#0#.png will read foo0.png, foo1.png, etc.; and foo#3#.png will generate foo000.png, foo001.png, etc. *It is important to format the filenames with a single dot '.' e.g. a filename formatted like T.f00000.ppm isn't supported, but Tf00000.ppm is okay, in this case you would pass the in argument with Tf#.ppm.*| | \--mbari-load-events=fileName \\ | \[\] | Load the event structure from a text file instead of computing it from the frames | | \--mbari-load-properties=fileName | \[\] \\ | Load the event property vector from a text file | | | | | | *Output Writng/Formatting* | | | | \--out= | required \\ | Value recomended is none. \\ | | \--\[no\]mbari-save-results \\ | \[no\] \\ | Save intermediate results in MBARI programs to disc | | \--\[no\]mbari-display-results | \[no\] | Display intermediate results in MBARI programs | | \--mbari-mark-interesting= | \[BoundingBox\] | Way to mark interesting events in output frames of MBARI programs | | \--mbari-opacity=<0.0 ... 1.0> | \[1.0\] | Opacity of shape or outline markings of events | | \--\[no\]mbari-mark-candidate \\ | \[yes\] | Mark candidates for interesting events in output frames of MBARI programs | | \--\[no\]mbari-mark-prediction \\ | \[no\] \\ | Mark the Kalman Filter's prediction for the location of an object in output frames of MBARI programs \\ | | \--\[no\]mbari-mark-foe | \[no\] | Mark the focus of expansion in the output frames of MBARI programs | | \--\[no\]mbari-save-output | \[no\] | Save output frames in MBARI programs | | \--\[no\]mbari-display-output | \[no\] | Display output frames in MBARI programs | | \--\[no\]mbari-label-events | \[yes\] \\ | Write event labels into the output frames \\ | | \--mbari-rescale-display=x | \[0x0\] | Rescale displays to x, or 0x0 for no rescaling \\ | | \--mbari-save-events=fileName | \[\] \\ | Save the event structure to a text file \\ | | \--mbari-save-properties=fileName \\ | \[\] \\ | Save the event property vector to a text file | | \--mbari-save-positions=fileName \\ | \[\] \\ | Save the positions of events to a text file | | \--mbari-save-event-num=ev1,ev1,...,evN; or: all | \[\] \\ | Save video clips showing specific events | | \--mbari-save-event-summary=fileName \\ | \[\] \\ | Save a human readable summary of all the events to a text file \\ | | \--\[no\]mbari-save-non-interesting-events \\ | \[yes\] \\ | If saving events, save non interesting events in addition to interesting event. Default is to not save non interesting events. \\ | | \--mbari-save-events-xml=fileName \\ | \[\] \\ | Save a XML output per all events | | \--mbari-source-metadata=fileName | \[\] \\ | Add video input source information to XML output \\ | | | | | | *Special Features* | | | | \--mbari-cache-size= | \[30\] | The number of frames used to compute the running average. \\ | | \--mbari-tracking-mode= \\ | \[KalmanFilter\] \\ | Way to mark interesting events in output of MBARI programs \\ | | \--mbari-segment-algorithm= | \[BinaryAdaptive\] \\ | Segmentation algorithm \\ | | \--mbari-mask-path= \\ | \[\] \\ | MaskPath: path to the mask image. *Important* this only masks the area to look for detections - it does not mask the area from the saliency computation. \\ | | \--mbari-mask-xposition= | \[1\] \\ | MaskXPosition: x position of the mask point of reference \\ | | \--mbari-mask-yposition= \\ | \[1\] | MaskYPosition: y position of the mask point of reference \\ | | \--mbari-mask-width= \\ | \[1\] | MaskWidth: mask width | | \--mbari-mask-height= \\ | \[1\] | MaskHeight: mask height \\ | | \--mbari-min-event-area= | \[34\] \\ | The minimum area an event must be to be candidate \\ | | \--mbari-max-event-area= \\ | \[1000\] \\ | The maximum area an event can be, to be candidate \\ | | \--mbari-saliency-dist= \\ | \[5\] \\ | The number of frames to delay between saliency map computations. Reduce this to improve your detection rate. Warning reducing this *will* increase your computation time. \\ |]]> 10911986 9830536 make make install {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision and AVED scripts|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts].\\ \\ \\ \\ \\ \\ \\]]> 9797767 9830535 ./configure make make install {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision and AVED scripts|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts].\\ \\ \\ \\ \\ \\ \\]]> 9797766 10387929 make install mpeg_encode /usr/local/bin {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision and AVED scripts|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts].\\ \\ \\ \\ \\ \\ \\]]> 10355194 13369379 13336611 13369382 13336614 13369381 13336613 13369378 cp make install mpeg_encode /usr/local/bin {noformat} When you are done, complete installation with [Step 6. Build and Install Mbarivision or Pmbarivision|mbarivision Installation - Step 6. Build and Install mbarivision or pmbarivision]. \\ \\ \\ \\ \\ \\ \\]]> 13336610 10387955 10355222 10387958 export XERCES_INCLUDE=/usr/include/xerces export XERCES_LIB=/usr/lib cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. {noformat} yum install XML::Xercesc {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software (optional)] (this step is only required if you need to convert video clips into a suitable format for processing with AVED).]]> 10355225 13369376 > /etc/ld.so.conf cpush /etc/ld.so.conf cexec ldconfig -v {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} Install the XML::Xerces library {noformat} export XERCESCROOT= export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} {tip:title=Handy Hint} If you installed the Xerces C+\+ library to a non-standard library location, be sure to add to the loader path in /etc/ld.so.conf the location, and run ldconfig -v to refresh the loader. If you installed to /usr/local or /usr no need to modify the loader. {tip} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|mbarivision Installation - Step 6. Build and Install mbarivision or pmbarivision], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|mbarivision Installation - Step 3. Build and Install Transcode].]]> 13336608 10387957 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software (optional)] (this step is only required if you need to convert video clips into a suitable format for processing with AVED).]]> 10355224 10387960 export XERCES_INCLUDE=/usr/include/xerces export XERCES_LIB=/usr/lib cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. {noformat} yum install XML::Xercesc {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software (optional)] (this step is only required if you need to convert video clips into a suitable format for processing with AVED).]]> 10355227 10387959 export XERCES_INCLUDE=/usr/include/xerces export XERCES_LIB=/usr/lib cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. {noformat} yum install XML::Xercesc {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software (optional)] (this step is only required if you need to convert video clips into a suitable format for processing with AVED).]]> 10355226 13369371 13336603 10387962 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P=/usr/local gmake sudo gmake install {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. {noformat} yum install XML::Xercesc {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} export XERCES_LIB=/usr/lib export XERCES_INCLUDE=/usr/include/xerces yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software (optional)] (this step is only required if you need to convert video clips into a suitable format for processing with AVED).]]> 10355229 10387961 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P=/usr/local gmake sudo gmake install {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. {noformat} yum install XML::Xercesc {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software (optional)] (this step is only required if you need to convert video clips into a suitable format for processing with AVED).]]> 10355228 13369369 13336601 10387964 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P=/usr/local gmake sudo gmake install {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. {noformat} export XERCES_LIB=/usr/lib export XERCES_INCLUDE=/usr/include yum install XML::Xercesc {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software (optional)] (this step is only required if you need to convert video clips into a suitable format for processing with AVED).]]> 10355231 10387963 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P=/usr/local gmake sudo gmake install {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. {noformat} export XERCES_LIB=/usr/lib export XERCES_INCLUDE=/usr/include/xerces yum install XML::Xercesc {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software (optional)] (this step is only required if you need to convert video clips into a suitable format for processing with AVED).]]> 10355230 10387966 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread -P=/usr/local gmake sudo gmake install {noformat} h3. Install XML::Xercesc This perl API to the xerces 2.7 library is required in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. {noformat} export XERCES_LIB=/usr/lib export XERCES_INCLUDE=/usr/include yum install XML::Xercesc {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software (optional)] (this step is only required if you need to convert video clips into a suitable format for processing with AVED).]]> 10355233 13369368 13336600 13369366 13336598 13369363 export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} {tip:title=Handy Hint} If you installed the Xerces C+\+ library to a non-standard library location, be sure to add to the loader path in /etc/ld.so.conf the location, and run ldconfig -v to refresh the loader. If you installed to /usr/local or /usr no need to modify the loader. {tip} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|mbarivision Installation - Step 6. Build and Install mbarivision or pmbarivision], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|mbarivision Installation - Step 3. Build and Install Transcode].]]> 13336595 10387970 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local/aved}} by default; of course you can change that with the usual {{\--prefix}} argument to {{configure}}. {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h2. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 10355237 13369364 13336596 10387969 export XERCESCROOT= {noformat} To build the mbarivision executable: {noformat} cd ./configure make make install {noformat} The install goes into {{/usr/local}} by default; of course you can change that with the usual {{\--prefix}} argument to {{configure}}. {tip:title=Handy Hint}If you update either the Mbarivision or Saliency source code, be sure to run a *make allclean*. This will clean not only the object files, but the a generated dependencies file that is used to compile each source file. The saliency toolkit changes fairly frequently and sometimes the dependencies change, so this ensures a clean build. {tip} h2. Installing AVED Scripts There is a simple install script that will install the AVED scripts we have developed over the years. The install script will copy the scripts to the /usr/local/aved/scripts directory and setup your user paths. {color:#990000}You will need to be root user to run this.{color} Install with the following:  {noformat} cd ./install {noformat}]]> 10355236 13369359 13336591 13369358 13336590 13369357 13336589 13369355 export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} {tip:title=Handy Hint} If you installed the Xerces C+\+ library to a non-standard library location, be sure to add to the loader path in /etc/ld.so.conf the location, and run ldconfig -v to refresh the loader. If you installed to /usr/local or /usr no need to modify the loader. {tip} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|mbarivision Installation - Step 6. Build and Install mbarivision or pmbarivision], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|mbarivision Installation - Step 3. Build and Install Transcode].]]> 13336587 13369353 export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} {tip:title=Handy Hint} If you installed the Xerces C+\+ library to a non-standard library location, be sure to add to the loader path in /etc/ld.so.conf the location, and run ldconfig -v to refresh the loader. If you installed to /usr/local or /usr no need to modify the loader. {tip} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|mbarivision Installation - Step 6. Build and Install mbarivision or pmbarivision], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|mbarivision Installation - Step 3. Build and Install Transcode].]]> 13336585 13369352 export XERCES_LIB=/usr/local/lib export XERCES_INCLUDE=/usr/local/include perl -MCPAN -e 'install XML::Xerces' {noformat} {tip:title=Handy Hint} If you installed the Xerces C+\+ library to a non-standard library location, be sure to add to the loader path in /etc/ld.so.conf the location, and run ldconfig -v to refresh the loader. If you installed to /usr/local or /usr no need to modify the loader. {tip} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files used in the AVED scripts. If you don't plan on using the AVED scripts, you can skip this step. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|mbarivision Installation - Step 6. Build and Install mbarivision or pmbarivision], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|mbarivision Installation - Step 3. Build and Install Transcode].]]> 13336584 10387949 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software (optional)] (this step is only required if you need to convert video clips into a suitable format for processing with AVED).]]> 10355216 10387951 cd $XERCESCROOT/src/xerces ./runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software (optional)] (this step is only required if you need to convert video clips into a suitable format for processing with AVED).]]> 10355218 10387952 10355219 10387953 10355220 10387954 10355221 10387850 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like --prefix, --enable-quitecompile, etc. but don't remove the options above. If you want to tinker with the saliency toolkit, copy it to a separate directory that you won't use in the AVED mbarivision build ! {warning} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 10355113 10387848 ./configure --enable-shared --prefix=/usr make sudo make install {noformat} h3. Building the Saliency Toolkit  When all Saliency dependencies are installed, the required build command to work with the AVED software, is the make _core_ and _tprogs_ build rules with the following command: {noformat} cd ./configure --without-qtdir --enable-force32 make core make tprogs {noformat} {warning:title=Warning} Don't change these configuration options or it will break the AVED mbarivision build in the last step. You can add options like --prefix, --enable-quitecompile, etc. but don't remove the options above. If you want to tinker with the saliency toolkit, copy it to a separate directory that you won't use in the AVED mbarivision build ! {warning} Now go get a cup of coffee, because this step takes a while. It took 28 minutes on a dual-XEON 2.4 GHz server. When you are done, go to [Step 2. Build and Install XML Libraries|AVED:AVED Installation - Step 2. Build and Install XML Libraries]]]> 10355111 10387843 cd $XERCESCROOT/src/xerces runConfigure -p linux -cgcc -xg++ -minmem -nsocket -tnative -rpthread gmake sudo gmake install {noformat} h3. Install the simple XML writer Install CPAN and add XML perl components for writing simple XML files. This is used in the AVED software scripts. This requires the perl-CPAN installer, if you don't have perl-CPAN installed, install it with: {noformat} yum install perl-CPAN {noformat} then, install the Simple and Writer modules with: {noformat} perl -MCPAN -e 'install XML::Simple' perl -MCPAN -e 'install XML::Writer' {noformat} When you are done, you can skip to [step 6|AVED:AVED Installation - Step 6. Build and Install Mbarivision and AVED scripts], or continue with the next optional step [AVED Installation Step 3. Build and Install Transcode Software|AVED:AVED Installation - Step 3. Build and Install Transcode Software (optional)] (this step is only required if you need to convert video clips into a suitable format for processing with AVED).]]> 10355106 11829334 11796572 20 2007-02-14 14:01:03.380 2015-01-06 11:30:35.870 5374092 6 false 0.0 0 0 8356125 6 false 0.0 AVED_Dissemination Migrate code to disseminate from moonjelly/CVS to kahuna/SVN Create examples of AVED workflow processing for MPEG, MOV, ASF, and AVI formats and put into SVN tree for export Create sourceforge site and upload mbarivision and aved ui code Remove environment variables from mbarivision configure to simplify the build Change install rule in pmbarivision to install schema ]]> 0 0 5374105 6 false 0.0 0 0 5374109 6 false 0.0 0 0 927 5 false 0.0 0 0 885 6 false 0.0 _AVED_system_integration_and_test Install mbarivision Install transcoding tools (transcode, ffmpeg) Install Java Install AVED UI Install AVED scripts ? Run automated test scripts Manuall test AVED GUI ]]> 0 0 2162699 5 false 0.0 0 0 9798412 5 false 0.0 0 0 11240565 6 false 0.0 0 0 2162701 5 false 0.0 0 0 2162702 5 false 0.0 0 0 5374134 6 false 0.0 0 0 917575 5 false 0.0 0 0 11240205 6 false 0.0 0 0 5374142 6 false 0.0 0 0 5374146 6 false 0.0 0 0 5374151 6 false 0.0 0 0 2162725 6 false 0.0 0 0 885 6 false 0.0 _AVED_Nice_To_Have Convert mbarivision/scripts from bash to perl ]]> 0 0 885 5 false 0.0 0 0 11240197 5 false 0.0 0 0 885 6 false 0.0 AVED_Nice_To_Have Fix graphcut bug in mbarivision application Convert mask code to morphological operator, instead of loop execution ]]> 0 0 885 6 false 0.0 _AVED_GUI_design Move /reference components in the aved-db common to both AVED and EITS to the package org.mbari.aved.utilities Integrate AVED API Test *all* mbarivision command options ]]> 0 0 11240205 5 false 0.0 0 0 2162701 6 false 0.0 0 0 2162725 5 false 0.0 0 0 2162702 6 false 0.0 0 0 885 6 false 0.0 0 0 5374197 5 false 0.0 0 0 2162699 6 false 0.0 0 0 11796998 6 false 0.0 0 0 5374197 6 false 0.0 0 0 11240565 5 false 0.0 0 0 885 6 false 0.0 AVED_Core_Updates Migrate all code on moonjelly CVS to SVN Create examples of AVED workflow processing for MPEG, MOV, ASF, and AVI formats Fix graphcut bug in mbarivision application ]]> 0 0 5374220 5 false 0.0 0 0 5374222 5 false 0.0 0 0 885 6 false 0.0 AVED_2006_tasks_to_complete Finish AVED UI dcline Convert homomorphic and Background Canny segmentation algorithms from Matlab to C++ ]]> 0 0 885 6 false 0.0 _AVED_subsystem_system_integration_and_test Install mbarivision Install saliency toolkit Install Tomcat webserver (VENUS only) Install transcoding tools(transcode, ffmpeg) Install AVED scripts ? Is this needed ? Test by running automated test scripts ]]> 0 0 5374109 5 false 0.0 0 0 5374105 5 false 0.0 0 0 5374134 5 false 0.0 0 0 8356125 6 false 0.0 0 0 5374220 6 false 0.0 0 0 11797304 6 false 0.0 0 0 5374222 6 false 0.0 0 0 10355915 6 false 0.0 0 0 5374151 5 false 0.0 0 0 718 5 false 0.0 0 0 5374146 5 false 0.0 0 0 5374142 5 false 0.0 0 0 6258689 6 false 0.0 0 0 885 6 false 0.0 _Miscellaneous Move AVED documentation from Tornado to Confluence dcline Update NFS mounts on AVED laptops dcline Update RaveHD software on Beowulffish dcline ]]> 0 0 927 6 false 0.0 0 0 885 6 false 0.0 AVED_2007_tasks_to_complete Populate AVED XML schema with input source information (frame width/height/rate) dcline Modify the AVED XML schema EventDetectionParameters to include *all* the mbarivision model options dcline Move/reference the components in aved-db common to both AVED and EITS to the package org.mbari.aved.utilities Clean up documentation on Tornado/move to confluence dcline Clean up mbarivision.C/segmentation.C to factor out MATLAB code into separate branch jerome Add 29.97 drop-frame calculation in libopenquicktime and transcode import_oqtmov.c dcline Clean up aved/scripts - archive old script, test all existing and update README dcline Copy JAMSTEC presentation from laptop to tornado share dcline Design AVED web services jerome Nice to have: convert bash scripts to perl jerome ]]> 0 0 917575 6 false 0.0 0 0 8356125 5 false 0.0 0 0 6258708 6 false 0.0 0 0 885 6 false 0.0 _AVED_subsystem_setup_for_dissemination Migrate all code on moonjelly CVS to SVN Setup SHERMAN as example clean system. ]]> 0 0 6258712 6 false 0.0 0 0 11797304 5 false 0.0 0 0 9798412 6 false 0.0 0 0 5374297 6 false 0.0 0 0 11240197 6 false 0.0 0 0 885 6 false 0.0 _AVED_API_design Design and test AVED API Design automated test scripts for JPG,PNG,PPM input Document AVED API Write user manual for operating AVED software without the GUI Write user manual for operating AVED with the GUI ]]> 0 0 11796998 5 false 0.0 0 0 5374085 5 false 0.0 0 0 6258689 5 false 0.0 0 0 718 6 false 0.0 0 0 5374085 6 false 0.0 0 0 10355915 5 false 0.0 0 0 5374092 5 false 0.0 0 0 6258708 5 false 0.0 0 0 5374297 5 false 0.0 0 0 6258712 5 false 0.0 0 0