==============================================================================
Minute of 2nd JLC physics meeting
 
Date: November 30, 1994
Place: KEK, 3rd building 1F meeting room.
 
1. Titles of the talks in the morning.
  1) Status of VTX and CAL R&D              by Y.Fujii     (KEK)
  2) Status of CDC R&D                      by T.Abe    (Nagoya)
  3) Status of SUSY WG                      by T.Tsukamoto (KEK)
  4) Report of ILC-TRC Experimentation WG   by T.Tauchi    (KEK)
 
   Copies of tranceparencies are kept in Miyamoto's office
   
 
2. Discussion in the afternoon.
  
---------------------
(I) Workstation Issue
---------------------
 
Several problems of the present JLC cluster were pointed out. Those were
 
 a) CPU power shortage.
        JIM takes 30sec/event, and present simulator takes 0.5sec/event.
        Either takes very long time to generate necessary data.
 b) Disk storage shortage.
        In order to store full data of WW pair creation corresponding 
        to 50fb-1, 14Gbytes  are needed. 
 c) Directory re-arrangement.
        1Gbytes home directory is too small,
        Set-path probles for VUE usage,
        Efficient distribution of storage sources,
        Duplicate archive of softwares,
        etc.....
 
Those were discussed in order that
 1) What is necessary for works toward Iwate '95, (Sep.'95),
 2) What should be done at KEK central computer system upgrade (Jan.'96),
 3) Directory re-arrangement.
 
[Discussions]
 
1) Toward Iwate'95
   *) CPU upgrade for existing HP's will not be done. Not cost-effective.
      Instead buy a new HP.
   *) Facom-equivalent CPU/Storage is necessary at least.
   *) Big-job execution is slower on Unix. This should be taken into account.
   *) Before Hawaii WS, jobs of only three persons fully occupied CPU's.
   *) Amount of storage didn't increase since Hawaii WS. 
   *) Universities can't afford 14Gbytes storage.
   *) Probably universities do not have to buy the storage by themselves.
   *) It is not necessary to store such a big data. 1Gbytes should be enough.
   *) For the Hawaii WS, data storage of about 10 CTL's were enough.
   *) Necessary Disk amount is unknown until we count for each reaction.
 
   ==> Do clever data organization and share data. Prepare standard data sets
       in a form that anyone can use them easily.
       Maybe we buy as much storage as we can.
 
2) Things at the central computer upgrade ; didn't take place
 
3) Directory re-arrangement
   *) Home directory is now 1Gbytes, which is too small.
   *) Only 1/3 of disks are accessible from anywhere.
   *) MO's are not effectively used.
   *) Buying a disk server ==> use upgraded KEK central computer.
 
   *) Several discussions about merits and demerits about distributing
      user home directories to several machines/directories, and about
      making symbolic link to user home directories.
 
   ==> Distribute users directories, make symbolic links to them so that
       directory structure looks the same.
     
       Common softwares should be put in a public space, and each user
       must not copy them to their own directory.
 
       Detail procedures will be E-mailed to users later
             
 
------------------------
(II) Mosaic organization
------------------------
 
Constant update of the JLC Mosaic was proposed. Also adition of new contents
were discussed as
     *) JLC introduction page update using Iwate seminor pictures,
     *) Manual pages,
     *) Group news,
     *) Transparency Library,
     *) Publication list.
Miyamoto-san and K.Fujii-san will make a skeletons for them.
 
[Comments]
*) Let subroups update thier section by themselves. Clarify who is in charge 
   but anyone can update.
   ==> Request to make a template. ( CDC group may make it ? )
*) Setup English pages and Japanese pages. Only one Japanese code will be 
   provided.
 
-------------------
(III) Odds and Ends
-------------------
 
1) 5th JLC workshop will be held at Kobe mid-Feburuary. Detail will be
   decided tomorrow, and announced soon.
  
2) Simplified JIM (FJIM) made.
   Full-spec JIM has no significant upgrade since the last meeting.
 
3) Procedure how to propose new R&D issue is not clear. When/where/whom
   to contact/propose must be public-announced.