Hotels in the area

To view available hotels in Alcalá for the meeting dates, please click here.

Recommended Hotels by closeness view map. to the meeting room at the Rector's office building:

Hostal Don Juan I or Hotel Apartamentos Don Juan I  0.5 km walking distance 7 min.
Hostal Miguel de Cervantes 0.4 km walking distance, 6 min.
Hostal Complutense Alcalá de Henares 0.5 km walking distance, 6 min.
Hotel Ciudad de Alcalá 0.75 km walking distance, 9 min.
RafaelHoteles Forum Alcalá 1.6 km walking distance, 20 min. Good hotel but only if you are interested in doing some sport.

Getting here from the Madrid Airport - Barajas

  • By Taxi

In the airport take a taxi to Alcalá de Henares. It take 20 minutes and costs around € 40,00.

  • By Metro & Train

If you Take the Metro line 8 (pink) from Terminal 4, Terminal 1, 2 or 3 of the Barajas Airport to "Nuevos Ministerios" metro station. Once at "Nuevos Ministerios", follow signs for commuter trains "Cercanias RENFE".You have to take separate tickets for Metro and Trains. Then, find the platform for trains C-7 line to "Alcala de Henares", or C-2 line whose end is "Guadalajara". You must get off at "Alcala de Henares" NOT at "Alcala de Henares Universidad" .

The trip from the airport to the train station in Alcalá de Henares takes about 1 hour and 30 minutes. The price of both tickets will be € 2.50 (Metro) and € 2.80 the train.

If you arrive at the Barajas Airport Terminal 4 you have the possibility to go to "Nuevos Ministerios" by the Train line C-1 and change platform for trains C-7 line to Alcala de Henares or C-2 to Guadalajara.

  • By Bus

Take bus No. 101 from the airport (T1, T2 and T3) to "Canillejas", last stop. The journey takes about 15 minutes. Here you should take the intercity bus No. 223, "ALSA" to take you to Alcalá de Henares. It also has to get off at the last stop. This journey takes about 25 minutes. The price of both tickets is € 1.50 a city bus and intercity bus 3.05, respectively.

From Terminals T1, T2 and T4 to "Canillejas" you can also take the bus line # 200 but its cost is € 2.50.

  • By Bus & Train

There is also an express bus from the airport terminals T1, T2 and T4, you are taken to the center of Madrid. Last stop is "Atocha" where you can take the train (lines C2 and C7) to Alcalá de Henares. The cost of the bus ticket is 2.00 €.

Getting here from Madrid

  • By car

By the A-2 highway to Zaragoza, take exit 23 to Alcala de Henares (Oeste). It takes about 30 minutes without trafic.

  • By train

From the train stations of Chamartin, Nuevos Ministerios, Recoletos and Atocha in Madrid, follow the signs for "Suburban Train". You can buy tickets at the stations, find the platform for trains C-7 line bound for Alcalá de Henares or line C-2 bound Guadalajara. Get off at the station of Alcala de Henares. It takes approximately 40 minutes and the fare is € 2.80

  • By Bus

Madrid is well connected with Alcalá de Henares, through the bus exchanger in Avenida de America (Avenida de América metro station). From here take the intercity bus No. 223, "ALSA" which has departures every 10-15 minutes. The ride will be approximately 40 minutes and the fare is 3.05 €.

Web page with transport information between Madrid and Alcalá de Henares is here.

Recommended restaurants

  • Going for tapas in Alcalá? Look here.

Information for remote connection

  • We expect to have a remote connection via (eg) skype for those who wish to join the discussions. During the first day, we'll make a final prioritization of the items to be addressed and set up the agenda for the rest of the week.


Developer meetings are traditionally informal (that is, we don't give a lot of presentations or have session conveners). Rather a list of topics is drawn up and we try to address them, often working in smaller groups when appropriate. If you are new to Offline, you should try to have the software installed prior to arrival so we don't spend too much time on that.

A non-exhaustive list of topics to be addressed follows:

  • Reading and writing TA-EUSO format
  • Event Data Model appropriate for JEM-EUSO
    • Component-wise and frame-wise access (how to make this design efficient and usable for both simulation and reconstruction)
  • Detector description UI appropriate for JEM-EUSO
    • Move hardwired parameters from files in G4TelescopeSimulator to XML
    • Top level hierarchy (eg. EUSO-X where X = TA, balloon, JEM, KLYPVE, mini ??)
    • Other items like
      • Pixel angle map
  • Automatic handling of Offline-EUSO interface setup in JAPE (?)
  • Strategy for remaining sim steps:
    • PMTs & pixels
    • Trigger
  • Reconstruction ?
  • Strategy for Geometry, reference CS.
  • Cloud camera progress and data storage strategy
  • GDAS data access/storage strategy
  • Back-porting improvements from NA61/SHINE (removal of .in files + better data manager)
  • Tutorial : how to write unit tests and acceptance tests





  • Tom presented some introductory available here
    • One note Tom mentioned was that TA-EUSO might be a sensible 1'st priority
    • Fausto noted that the Balloon PDM may be ready first
    • Lech noted that the data packets will be the same for TA-EUSO and EUSO-Balloon
    • Mario will get some feedback on this issue during the simulation skype call tomorrow
  • Lech is working on a ROOT-tree format into which data packets can be converted which may be more convenient to use as an Offline format. He expects to have a prototype ready soon. Further information available on the EUSO TA page.

Possible modifications to detector structure

  • Fausto suggested we begin with the new detector description structure for JEM-EUSO. The prototype structure is below.
  • Note that this structure will represents the "Branches" of the "Tree" (not in the ROOT sense, but in the metaphorical sense). Below the "Branches" smaller "Leaves" will exist with additional details. What we are thinking at the moment is that the Event and Detector will follow the same Tree, Branch structure but will have different leaves. For instance, the Event structure, the Event Pixel will contain real and simulated traces, while the Detector Pixel will contain information on health of the Pixel, location, etc.
    • Eye (could be TA-EUSO, EUSO-Balloon, JEM-EUSO, K-EUSO, Kx3 or some combination thereof (eg. euso + miniEuso on ISS)
      • Telescope (potential for 3 telescopes for the Kx3 option)
        • Lense ( 3 or 2 in case of JEM-EUSO, EUSO-Balloon, TA-EUSO)
        • CCB (?) 18 (8-9 PDM's / CCB)
          • L2 trigger (CCB-LTT trigger) ?
          • PDM (x137. 36 PMTs/PDM = 9 ECs/PDM = 2304 Pixels/PDM)
            • L1 trigger ( PTT - persistent tracking trigger)
            • EC (x9, PMT readout performed at this level via ASIC. Count integration performed at 1 GTU = 2.5 µs)
              • PMT ( 8x8 Pixel = 64 Pixel )
                • Pixel

Offline xml vs ESAF dat files

  • Conversion of original ESAF dat files to xml files using cmake during the build (no need for hand-modification of files)
  • xml camera layout should probably follow SdStationList? instead of FdModel?
    • Irregular geometry of SD array vs Row/Column? of FD camera
    • JEM-EUSO camera is irregular (and changing every half a year)
    • Row/Column? could be used from PDM level downwards

CMake fiasco

  • We inherited a lot of CMake crapification from Auger. For eg. check the differences between CMakeLists in FDetector and SDetector regarding how the ".in" files are created and moved to build and install areas. Someone needs to read the documentation and do it properly.

general cleanup

  • should employ Component and other utilities from Shine/Framework/Detector/Utilities?
  • consider used of boost::noncopyable in Event (Detector). In Event do we want to allow public copy c'tors at branch level, however?
  • consider replacing STL containers of pointers / indirect_iterator combinations with boost::ptr_vector
  • Managers...


  • Writer (Lech's TTrees EUSO TA)
  • Reader
JSN Tendo template designed by