| 34 | This is a very basic first step, and only establishes basic connectivity. A better test involves interacting with |
| 35 | some data. This can be done with the show_info command. Both show_info and the underlying idea of |
| 36 | storage unit numbers (sunums) are beyond the scope of this discussion, and are introduced here only in passing. For |
| 37 | now, we use show_info to identify data that we do not have on disk already. The command : |
| 38 | |
| 39 | {{{ |
| 40 | show_info -S -P key=T_OBS,T_REC_INDEX,WAVELNTH ds='aia.lev1[2011-08-19T10:59:57Z/1m][?wavelnth=304?]' |
| 41 | }}} |
| 42 | |
| 43 | will return something like this if the data are already on disk : |
| 44 | |
| 45 | {{{ |
| 46 | sunum T_OBS T_REC_INDEX WAVELNTH SUDIR |
| 47 | 236661975 2011-08-19T10:59:57.57Z 1092826832 304 /SUM02/D236661975/S00000 |
| 48 | 236662019 2011-08-19T11:00:09.57Z 1092826844 304 /SUM02/D236662019/S00000 |
| 49 | 236662008 2011-08-19T11:00:21.57Z 1092826856 304 /SUM01/D236662008/S00000 |
| 50 | 236662040 2011-08-19T11:00:33.59Z 1092826868 304 /SUM02/D236662040/S00000 |
| 51 | 236662058 2011-08-19T11:00:45.57Z 1092826880 304 /SUM01/D236662058/S00000 |
| 52 | }}} |
| 53 | |
| 54 | but will not list the directories where the data reside if the data are not on disk : |
| 55 | |
| 56 | |
| 57 | {{{ |
| 58 | sunum T_OBS T_REC_INDEX WAVELNTH SUDIR |
| 59 | 236661975 2011-08-19T10:59:57.57Z 1092826832 304 |
| 60 | 236662019 2011-08-19T11:00:09.57Z 1092826844 304 |
| 61 | 236662008 2011-08-19T11:00:21.57Z 1092826856 304 |
| 62 | 236662040 2011-08-19T11:00:33.59Z 1092826868 304 |
| 63 | 236662058 2011-08-19T11:00:45.57Z 1092826880 304 |
| 64 | }}} |
| 65 | |
| 66 | If we find some data that are not on disk, then we can initiate a JMD download of the data by using the "-p" rather |
| 67 | than the "-P" option with show_info, like this : |
| 68 | |
| 69 | {{{ |
| 70 | show_info -S -p key=T_OBS,T_REC_INDEX,WAVELNTH ds='aia.lev1[2011-08-19T10:59:57Z/1m][?wavelnth=304?]' |
| 71 | }}} |
| 72 | |
| 73 | The download should then appear in the JMD log, and subsequently running show_info with "-P" should show the data to be on disk locally. |
| 74 | |
| 75 | |
| 76 | If requesting the data with show_info fails, this may indicate the the JMD is running but is not contactable through show_info. To |
| 77 | query the database directly, use the jmd_admin.pl script to request the data directly from the JMD : |
| 78 | |
| 79 | |
| 80 | {{{ |
| 81 | jmd_admin.pl --request -- --series=aia.lev1 --sunums= 236661975, 236662019, 236662008, 236662040, 236662058 --priority=20 |
| 82 | }}} |