You have to be logged in to leave a comment.
Sign In
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
SIMPLE = T / data conform to FITS standard BITPIX = 32 / bits per data value NAXIS = 0 / number of data axes EXTEND = T / File may contain standard extensions NEXTEND = 1 / Number of standard extensions GROUPS = F / image is in group format DATE = '2010-04-17' / date this file was written (yyyy-mm-dd) FILENAME= 'fb1x2e04j_jit.fits ' / name of file FILETYPE= 'JTB ' / type of data found in data file TELESCOP= 'HST' / telescope used to acquire data INSTRUME= 'FGS ' / identifier for instrument used to acquire data EQUINOX = 2000.0 / equinox of celestial coord. system OPUS_VER= 'OPUS 2010_1 ' / OPUS software system version number PDB_VER = 'CCS ' / Project Database version in use ROOTNAME= 'fb1x2e04j ' / rootname of the observation set TARGNAME= 'VY-REF-4 ' / proposer's target name PROC_TYP= 'NORMAL ' / type of pipeline processing CONFIG = 'FGS ' / proposed instrument configuration PROPOSID= 11789 / PEP proposal identifier PROGRMID= 'B1X' / program id (base 36) / ASSOCIATION KEYWORDS ASN_ID = 'NONE ' / unique identifier assigned to association ASN_TAB = 'NONE ' / name of the association table END XTENSION= 'BINTABLE' / extension type BITPIX = 8 / bits per data value NAXIS = 2 / number of data axes NAXIS1 = 114 / length of first data axis NAXIS2 = 46 / length of second data axis PCOUNT = 0 / number of group parameters GCOUNT = 1 / number of groups TFIELDS = 28 / number of fields in each table row INHERIT = T / inherit the primary header EXTNAME = 'jit ' / extension name EXTVER = 1 / extension version number ROOTNAME= 'fb1x2e04j ' / rootname of the observation setEXPNAME = 'fb1x2e04j ' / exposure identifier OBSET_ID= '2E' / observation set id PROCTIME= '2010.107:00:08:55 ' / Date-Time When Observation Processed / JITTER TABLE COLUMNS TTYPE1 = 'Seconds ' / three second intervals from start TUNIT1 = 'seconds ' / units of field 1 TFORM1 = 'E ' / format in which field 1 is coded TTYPE2 = 'V2_dom ' / dominant FGS V2 coordinate TUNIT2 = 'arcsec ' / units of field 2 TFORM2 = 'E ' / format in which field 2 is coded TTYPE3 = 'V3_dom ' / dominant FGS V3 coordinate TUNIT3 = 'arcsec ' / units of field 3 TFORM3 = 'E ' / format in which field 3 is coded TTYPE4 = 'V2_roll ' / roll FGS V2 coordinate TUNIT4 = 'arcsec ' / units of field 4 TFORM4 = 'E ' / format in which field 4 is coded TTYPE5 = 'V3_roll ' / roll FGS V3 coordinate TUNIT5 = 'arcsec ' / units of field 5 TFORM5 = 'E ' / format in which field 5 is coded TTYPE6 = 'SI_V2_AVG ' / mean jitter in V2 over 3 seconds TUNIT6 = 'arcsec ' / units of field 6 TFORM6 = 'E ' / format in which field 6 is coded TTYPE7 = 'SI_V2_RMS ' / rms jitter in V2 over 3 seconds TUNIT7 = 'arcsec ' / units of field 7 TFORM7 = 'E ' / format in which field 7 is coded TTYPE8 = 'SI_V2_P2P ' / peak jitter in V2 over 3 seconds TUNIT8 = 'arcsec ' / units of field 8 TFORM8 = 'E ' / format in which field 8 is coded TTYPE9 = 'SI_V3_AVG ' / mean jitter in V3 over 3 seconds TUNIT9 = 'arcsec ' / units of field 9 TFORM9 = 'E ' / format in which field 9 is coded TTYPE10 = 'SI_V3_RMS ' / rms jitter in V3 over 3 seconds TUNIT10 = 'arcsec ' / units of field 10 TFORM10 = 'E ' / format in which field 10 is coded TTYPE11 = 'SI_V3_P2P ' / peak jitter in V3 over 3 seconds TUNIT11 = 'arcsec ' / units of field 11 TFORM11 = 'E ' / format in which field 11 is coded TTYPE12 = 'RA ' / Right Ascension of aperture reference TUNIT12 = 'degrees ' / units of field 12 TFORM12 = 'D ' / format in which field 12 is coded TTYPE13 = 'DEC ' / declination of aperture reference TUNIT13 = 'degrees ' / units of field 13 TFORM13 = 'D ' / format in which field 13 is coded TTYPE14 = 'Roll ' / position angle between north and +V3 TUNIT14 = 'degrees ' / units of field 14 TFORM14 = 'D ' / format in which field 14 is coded TTYPE15 = 'LimbAng ' / angle between V1 axis and Earth limb TUNIT15 = 'degrees ' / units of field 15 TFORM15 = 'E ' / format in which field 15 is coded TTYPE16 = 'TermAng ' / angle between V1 axis and terminator TUNIT16 = 'degrees ' / units of field 16 TFORM16 = 'E ' / format in which field 16 is coded TTYPE17 = 'LOS_Zenith' / angle between HST zenith and target TUNIT17 = 'degrees ' / units of field 17 TFORM17 = 'E ' / format in which field 17 is coded TTYPE18 = 'Latitude ' / HST subpoint latitude TUNIT18 = 'degrees ' / units of field 18 TFORM18 = 'E ' / format in which field 18 is coded TTYPE19 = 'Longitude ' / HST subpoint longitude TUNIT19 = 'degrees ' / units of field 19 TFORM19 = 'E ' / format in which field 19 is coded TTYPE20 = 'Mag_V1 ' / magnetic field along V1 TUNIT20 = 'Gauss ' / units of field 20 TFORM20 = 'E ' / format in which field 20 is coded TTYPE21 = 'Mag_V2 ' / magnetic field along V2 TUNIT21 = 'Gauss ' / units of field 21 TFORM21 = 'E ' / format in which field 21 is coded TTYPE22 = 'Mag_V3 ' / magnetic field along V3 TUNIT22 = 'Gauss ' / units of field 22 TFORM22 = 'E ' / format in which field 22 is coded TTYPE23 = 'BrightLimb' / Earth limb of LimbAng is bright (1 or 0) TUNIT23 = ' ' / units of field 23 TFORM23 = 'I ' / format in which field 23 is coded TTYPE24 = 'FGS_flags ' / FGS status flags TUNIT24 = ' ' / units of field 24 TFORM24 = 'E ' / format in which field 24 is coded TTYPE25 = 'DayNight ' / observation taken during day (1) or night (0) TUNIT25 = ' ' / units of field 25 TFORM25 = 'I ' / format in which field 25 is coded TTYPE26 = 'Recenter ' / recentering status flag, event in progress = 1 TUNIT26 = ' ' / units of field 26 TFORM26 = 'I ' / format in which field 26 is coded TTYPE27 = 'TakeData ' / vehicle guiding status, nominal GS tracking = 1TUNIT27 = ' ' / units of field 27 TFORM27 = 'I ' / format in which field 27 is coded TTYPE28 = 'SlewFlag ' / vehicle slewing status, slewing = 1 TUNIT28 = ' ' / units of field 28 TFORM28 = 'I ' / format in which field 28 is coded END @<ÌÌÄ50ŽBp¼¡Ãº6ÎÄ)l89…µ¼:è6à;æm#¹N`ü:Ð+Ð;߬b@`³óM±6HÀ7…’=1f�@pñ’¶#ÔfBjE{š BYý¿A#¢ÌB¯E—¾,2>uÂŒ½ IP������������@¾ffÄ50—Bp¼úú6ÕÄ)l2¹IVº:ÄSˆ;à´9å’]:Ò½Ä;Ĭã@`³óNÐøÀ7…’;*«@pñ’Ã>fiBjÒ{š BYAâA"IúB¯–ˆ¾,2>uÂŒ½ IP������������A33Ä50‘Bp¼dú6ºÄ)l>9·ˆ:™$n;²í/¸´„Ï:«x¥;¶=@`³óMÂì|À7…’=¥H¢@pñ’ÉZw„Bk�»{š BX†
Press p or to see the previous file or,
n or to see the next file
Comments
Integrate AWS S3
Use S3 remote
Select bucket
Access key
Finish
Use AWS S3 as storage!
Browsing data directories saved to S3 is possible with DAGsHub. Let's configure
your repository to easily display your data in the context of any commit!
Existing keys:
s3://stpubdata/hst
Jan 31, 2023
Specify your S3 bucket
Select Region
af-south-1 - Africa (Cape Town)
ap-northeast-1 - Asia Pacific (Tokyo)
ap-northeast-2 - Asia Pacific (Seoul)
ap-south-1 - Asia Pacific (Mumbai)
ap-southeast-1 - Asia Pacific (Singapore)
ap-southeast-2 - Asia Pacific (Sydney)
ca-central-1 - Canada (Central)
eu-central-1 - EU (Frankfurt)
eu-north-1 - EU (Stockholm)
eu-west-1 - EU (Ireland)
eu-west-2 - EU (London)
eu-west-3 - EU (Paris)
sa-east-1 - South America (São Paulo)
us-east-1 - US East (N. Virginia)
us-east-2 - US East (Ohio)
us-gov-east-1 - US Gov East 1
us-gov-west-1 - US Gov West 1
us-west-1 - US West (N. California)
us-west-2 - US West (Oregon)
Congratulations!
hst-dataset is now integrated with AWS S3!
Delete Storage Key
Are you sure you want to delete this access key?
No
Yes
Integrate Google Cloud Storage
Use Google Storage
Select bucket
Upload key
Finish
Use Google Cloud Storage!
Browsing data directories saved to Google Cloud Storage is possible with DAGsHub. Let's configure
your repository to easily display your data in the context of any commit!
Specify your Google Storage bucket
Congratulations!
hst-dataset is now integrated with Google Cloud Storage!
Delete Storage Key
Are you sure you want to delete this access key?
No
Yes
Integrate Azure Cloud Storage
Use Azure Storage
Select bucket
Set key
Finish
Use Azure Cloud Storage!
Browsing data directories saved to Azure Cloud Storage is possible with DAGsHub. Let's configure
your repository to easily display your data in the context of any commit!
Specify your Azure Storage bucket
Congratulations!
hst-dataset is now integrated with Azure Cloud Storage!
Delete Storage Key
Are you sure you want to delete this access key?
No
Yes
Integrate S3 compatible storage
Use S3 like remote
Select bucket
Access key
Finish
Use any S3 compatible storage!
Browsing data directories saved to S3 compatible storage is possible with DAGsHub. Let's configure
your repository to easily display your data in the context of any commit!
Specify your S3 bucket
Bucket name cannot be the same as the repository name. Please change one of them.
Check this box only if you trust this domain, otherwise your data and credentials might be
stolen by man in the middle or spoofing attacks.
Congratulations!
hst-dataset is now integrated with your S3 compatible storage!
Models
Annotations
Connect to our Discord channel