Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  14 Jul 2004, Piotr Zolnierczuk, , future direction discussion? 
    Reply  14 Jul 2004, Piotr Zolnierczuk, , future directions discussion? 
    Reply  14 Jul 2004, Stefan Ritt, , future direction discussion? 
       Reply  15 Jul 2004, Konstantin Olchanski, , future direction discussion? 
Message ID: 24     Entry time: 14 Jul 2004     In reply to: 23
Author: Piotr Zolnierczuk 
Subject: future directions discussion? 
Sorry the previous message got mangled:

I think that rather than spending too much time on where to put files 
and how to define the environment - I am guilty of that myself -  we should 
perhaps have some discussion on the future of MIDAS. 

Are we ready for 2.0? 

Stefan - do you have any ideas/enhancements? 

1) For one I would like to explore memory mapping (mmap()) on Linux.
I've used it once upon a time on DEC OSF/1 and I found it really nice 
compared to shared memory. From a user standpoint it behaves as a shared
memory but is mapped to a real file that can be easily "removed" when 
neccessary. One really annoying thing in MIDAS is when it goes ballistic 
the cleanup is somewhat tricky. 
The question if there is any performance penalty associated 

2) Expanding hardware support: 
  a) custom microcontrolers? 
  b) other hardware
  c) how about a "standard" Linux device /dev/midas for various 
  PCI cards (PCI<->CAMAC) (PCI<->VME) 

3) I have never really seen a midas deployment that uses interrupts. 
I do understand the ease of polling and the fact that these days CPU's 
are cheap but sometimes it is important to use interrupts. 

Any examples/experience? 


ELOG V3.1.4-2e1708b5