Dear Astrid, some of my comments I will also incorporate to the coordination duty document, but nevertheless I shall write them also here. >1) First, to summarize the instruments and times, and see if I am >right + some questions. > >TRACE: 20-31/8 > 3-20/8 we get obs. time whenever possible (filament campaign etc) > time: 7:00-13:30 UT Completely right. Send each day your pointing request to the trace_planner. It seems they will follow your wish each day until 20. Just maybe once Bloomfield (HOP026) will start to ask TRACE support problems can appear. But they target is QS so at least for some days we can have common target. Later (starting Aug 20) TRACE team has promised to support us. Conflicting campaign HOP034 have asked for the TRACE time later then we, so we have a priority according to the TRACE policy. Nevertheless I expect there will be no problem to cooperate as they will have a person at SST for their campaign. >Hinode: 18-23/8 > After that, we can try to follow same target if we get the > Hinode/EIS pointing info in time > time: ??? They will accept our pointing for the days you have mentioned. For the rest of the days (13-17,24-31) you can only see Hinode web page for the planned pointing and to decide whether you will move 'your' instruments - DOT, TRACE, CDS to their target. Where to find that information is explained in item 2/ in aux.txt file ('Auxiliary info' item at the web page). >SoHO/ Do I understand this right that there will be no SoHO support after >MDI,CDS 17/8 due to keyhole? Does this means that we do not send any more > info to the SOHO instrument contact persons from 17/8 on? > Or should we still send it just in case? > time: 7:00-13:30 UT (CDS: 06:40-13:40 UT) This I prefer to check again as it was mentioned that the actual time slot of the keyhole depends on the actual evolution of the SOHO trajectory. Email to CDS planner was sent. MDI will be in FD from tomorrow until end of the month but almost without high rate. I shall write and email to MDI planner valid until the end of August so I expect you will not need to communicate with MDI. >As for the CDS study mode, is it now always Vardyn_A (following your emails >with P. Young)? Or should we use Varadyn_A for QS and Varadyn_B for AR study? The difference seems to be that C and D use the 2" slit rather than the 4" slit (A and B). So C definitely when you expect flares, A when flare chance is low - QS or weak AR as 10966. Decision for VARDYN_A for the last few days with AR 10966 was made by Peter Young. >2) As regards the emails to be sent out each day. Before the beginning of >the campaign you had sent out an email to each of the instruments planners >(which were also copied to us) with details on the study. Did you then >send extra emails to each of the instruments planner also every day >or only the one with the pointing info which we also received? I was sending just pointing information. >Did you usually receive a confirmation from each of the planners to >your daily emails? Yes, from TRACE regularly. From MDI and CDS only for some days. >3) Hinode: This is the part where I am most anxious. >Can you please help me/us with the info that should be sent to the Hinode >planners of the EIS, XRT and SOT instruments. >From what I saw from your email correspondence, the EIS study seems to be >settled but still it should be declared in a first email to the planner I guess. EMAIL from EIS - Culhane: I will shortly send you the name of the EIS Chief Observer who will be running EIS during your observation. From 13 August you should establish contact with him through email to eis_co@solar.isas.jaxa.jp. Always remember to put "eis_co:" in the subject line of any messages you send to eis_co. Until then you should continue to interact with me. So please sent email to eis_co@solar.isas.jaxa.jp with "eis_co:" in the subject checking if they are ready: days: 18-23/8 time: 08-12UT EIS procedure: two EIS Studies 196 (context_calib_jr - a raster) and 197 (obs_sit_stare_jr - sit-and-stare mode (SNS acronym is used by EIS team)) - see them at http://msslxr.mssl.ucl.ac.uk:8080/SolarB/EisStudyList.jsp . The following mixture of these two studies was asked to be run: 08:00 - Study 196 - 3times then - Study 197 - N times (till ~09:30), in center of the previous rasters then - stop for 15 minutes, for EIS tables upload then - Study 197 - M times, the same slit position then - Study 196 - 3times (till ~12:00), rasters centered around previous slit They should reply 'yes of course'... >As for SOT and XRT, this is all very unclear to me how this shall be handled. For me as well! SOT: This was sent to SOT team as our final wish after some discussion with them and some changes made (item 'Hinode/SOT details' at our web page): - FOV: 109" x 109" (1k x 1k pxs) - binning: 2 x 2 pxs - 3bit JPEG compression - spectral channels: sequentially in time BFI: G-band, Ca II H, NFI: Fe I 630.25nm long. magnetograms - cadence: 10s per filtergram (30s per sequence of 3 selected channels) - telemetry needed: 300kbps - total run duration: 6.5 hours (07:00-13:30 UT) - no compensation of the solar rotation - targets: - an ctive region when located near the disk center (microflares) - quiet Sun near disk center when no activity is present there (solar network) - pointing: specified via e-mail a day in advance Please repeat this request to sot_co on Aug 13. Maybe they will answer with shortening the time slot (this was announced by EIS just to 08-12UT). XRT: This was sent to SOT team as our final wish (item 'Hinode/XRT details'): - high cadence of the images using just one selected filter using - no binning - loss-less compression - no compensation of the solar rotation - targets: - an active region when located near the disk center (microflares) - quiet Sun near disk center when no activity is present there (solar network) - pointing: specified via e-mail a day in advance Microflare mode: 256x256 px, thin Be filter, exposure max. 1s with AEC, cadence 10s Network mode : 384x384 px, thin-Al/Mesh, exposure max. 15s with AEC, cadence 15s Golub replied that they will contact us in case of comments. Nothing has appeared as program is so simple. This request should be repeated as well announcing that beside the target you will send each day also information on the mode selected. Generally, EIS was asked to be contact instrument for our HOP therefore discussion on days/time slot have been carried out only with Culhane. He finally informed with dates 18-23/8 and. Time slot: EIS: 08-12, SOT and XRT should join us for this period and target selected. I suppose they will follow this way as our HOP020 was included to the Hinode program at http://www.isas.jaxa.jp/home/solar/hinode_op/hop.php?hop=0020 where this information is basically given. I apologize that I was not contacting the Hinode teams during this week but this seems to be to early. They are busty with program of this week. As we start only at the end of the next week 33 it is better to contact them on Monday 13 (or sending email during the weekend). >At our webpage http://www.uni-graz.at/igam-sophy/Download/dot_07 >where we (Sigrid, Manu and myself) will update the relevant documents, >I tried to build up the same structure as yours (in particular the >subdirectories under /obs for each of the observing day where we >will out the quicklook images), so that it should be convinient to combine >all files at the end. There are now also all 5 files for the campaign, >which I will update on monday with the recent files from your homepage. >Please let me know if you see some inconsistency. No, perfectly prepared. I hope you have enough space for huge volume of the quicklook data... On the other hand at http://www.astro.sk/~choc/open/07_dot/ you will see more information than linked directly at http://www.astro.sk/~choc/open/07_dot/07_dot.html . subdirectories: hinode/, obs/, others/, soho/..., trace/ with all my correspondence with them - including email log (XXX_s - sent to XXX, XXX - received from XXX). and files which are used for the web page: 07_dot.html aux.txt coordination_duties.txt eis_rybak_science_case_v2.txt eis_rybak_v2.txt jop_proposal.txt notes.txt operation_duties.txt planning.txt rybak_dot_2007.tex rybak_dot_proposal_2007.pdf rybak_hinode_proposal.pdf rybak_hinode_proposal.tex sot_rybak_v2.txt summary.txt xrt_rybak_v2.txt and files I have sent a requests for pointing: request_0308.txt request_04-06_08.txt request_07_08.txt request_08_08.txt request_09_08.txt request_10_08.txt request_11-13_08.txt plus so other: addresses.txt all_s1.txt In case of a need please check them. >To finish with something positive: There exists at least already some rough >draft by Manu on the CME study of the event from last years campaign + >another event, which we will send to you (after revisions) by 24 August as we >had discussed. I looking forward to read it!