HR-e dZddlZddlZddlmZddlmZddlmZ ddl m Z gdZ Gdd e j ZeZdd Zdd Z ddZddZddZddZgdfdZejdZdZGdde ZGddeeZGddeeZGddeeZGdd eeZ Gd!d"ee!Z"Gd#d$eZ#Gd%d&eZ$Gd'd(eZ%Gd)d*eZ&Gd+d,eZ'Gd-d.eZ(Gd/d0eZ)Gd1d2eZ*Gd3d4eZ+Gd5d6eZ,Gd7d8eZ-Gd9d:eZ.Gd;deZ0Gd?d@eZ1GdAdBeZ2GdCdDeZ3GdEdFeZ4GdGdHeZ5GdIdJeZ6GdKdLe Z7GdMdNee8Z9GdOdPe Z:GdQdReZ;GdSdTeZ<GdUdVeZ=GdWdXeZ>GdYdZeZ?Gd[d\eZ@Gd]d^eZAGd_d`eZBGdadbeZCGdcddeZDGdedfeZEGdgdheZFGdidjeZGGdkdleZHGdmdneZIGdodpeZJGdqdreZKGdsdteZLGdudveZMGdwdxee!ZNGdydzeZOGd{d|eZPGd}d~eZQGddeZRGddeZSGddeZTGddeZUGddeZVGddeZWGddeZXGddee!ZYGddee!ZZGddee!Z[Gddee!Z\Gddee!Z]Gddee!Z^Gddee!Z_Gddee!Z`Gddee!ZaGddee!ZbGddee!ZcGddee!ZdGddee!ZeGddee!ZfGddeZgGddee!ZhGddee!ZiGddee!ZjGdde"ZkGddee!ZlGddee!ZmGddeZnGddee!ZoGddeZpdZqdZreejsd ierZe tdeqdDe tdeqd¦DdS)aVOTable exceptions and warnings. .. _warnings: Warnings -------- .. note:: Most of the following warnings indicate violations of the VOTable specification. They should be reported to the authors of the tools that produced the VOTable file. To control the warnings emitted, use the standard Python :mod:`warnings` module and the ``astropy.io.votable.exceptions.conf.max_warnings`` configuration item. Most of these are of the type `VOTableSpecWarning`. {warnings} .. _exceptions: Exceptions ---------- .. note:: This is a list of many of the fatal exceptions emitted by ``astropy.io.votable`` when the file does not conform to spec. Other exceptions may be raised due to unforeseen cases or bugs in ``astropy.io.votable`` itself. {exceptions} N)dedent)warn)config)AstropyWarning)Confconf warn_or_raisevo_raise vo_reraisevo_warnwarn_unknown_attrsparse_vowarning VOWarningVOTableChangeWarningVOTableSpecWarningUnimplementedWarning IOWarningVOTableSpecErrorc8eZdZdZejdddZdS)rzG Configuration parameters for `astropy.io.votable.exceptions`. zMNumber of times the same type of warning is displayed before being suppressedinteger)cfgtypeN)__name__ __module__ __qualname____doc___config ConfigItem max_warnings=lib/python3.11/site-packages/astropy/io/votable/exceptions.pyrr=s<&7% WLLLr!rc v|i}|d}|dd}|d|dd|dd|d| S)N)?r$filenamer$:r: )get)messagenamerposr%s r"_format_messager-Ls] ~ {zz*c**H = =Q = =#a& = =D = =G = ==r!cdt|}|dt|d|d|xxdz cc<|d|}|tjkr6|tjkr|xjdz c_t ||dzdSdS)N_warning_countsrr'z/ (suppressing further warnings of this type...) stacklevel)type setdefaultdictrrformatted_messager)warningrr2 warning_class message_counts r"_suppressed_warningr:UsMMM '00;;M1MMM m,,,1,,,,-mr?rr,s r"r r vs"~ /$ , ,,r!cB|i}tt||jj||}|dt|dkrt|}t |r|d|zz }|f|_|)z Raise an exception, with proper position information if available. Restores the original traceback of the exception, and should only be called within an "except:" block of code. Nr )r-str __class__rsplitlenr?)excrr, additionalr*s r"r r s~c#hh (>LLG}}qSXX^^--a000c(( :$3##zCH Ir!c|i}|dddkr$||||}t|||dzdSdS)z> Warn, with proper position information if available. Nr<rignorer'r1)r)r:)r8r?rr,r2r7s r"r r sc~zz(F##x//-fc22GV QGGGGGG0/r!c T|D]$}||vrtt||f|||dz%dS)Nr'r1)r W48)elementattrsrr, good_attrr2attrs r"r r sLRR y C$&#*q. Q Q Q QRRr!zO:?(?P[0-9?]+):(?P[0-9?]+): ((?P[WE]\d+): )?(?P.*)$cTi}t|}|r@|dx|d<}|u|ddk|d<|d |d<t |ddd|d<d ||d <nd |d<d |d<d |d <d|d<d|d < t |d|d<n#t $rd|d<YnwxYw t |d|d<n#t $rd|d<YnwxYw|d|d<d |d<nHd|d<d |d<d |d<d |d <d |d<t|ts| d}||d<|S)z; Parses the vo warning string back into its parts. r7NrW is_warning is_exceptionr'numberzio/votable/api_exceptions.html#doc_urlFTis_othernlinencharrestr* is_somethingutf-8) _warning_patsearchgroupupperintlower ValueError isinstancerEdecode)lineresultmatchr7s r"rrs F    % %E !&+kk)&<&<<yG  #*1:#3#3#5#5# ""5;;y#9#9!""#=>>F8  S'--// S SF9  #(F< %*F> "!%F: #F8  $F9  !%++g"6"677F7OO   F7OOO  !%++g"6"677F7OO   F7OOO !KK//y!%~ y$|!&~"z!&~$$$ (;;w''D y Ms$ %C11DD%D--D?>D?c>eZdZdZdZdZddZdZedZ dS) rz The base class of all VO warnings and exceptions. Handles the formatting of the message with a warning or exception code, filename, line and column number. r rBNc|i}t|ts|f}|jj|}t ||jj|||_t ||jdSN) rftuplemessage_templateformatr-rFrr6Warning__init__)selfr?rr,msgs r"rrzVOWarning.__init__sx >F$&& 7D*d#*D1!0 (&#" "  t566666r!c|jSrm)r6)rss r"__str__zVOWarning.__str__s %%r!c`t|jr|jj|jS|jSrm)rH default_argsrorp)clss r"get_short_namezVOWarning.get_short_names5 s  B.3'.0@A A##r!NN) rrrrrxrorrrv classmethodrzr r!r"rrsiL 7 7 7 7&&&$$[$$$r!rceZdZdZdS)rz7 A change has been made to the input XML file. Nrrrrr r!r"rrr!rceZdZdZdS)rzS The input XML file violates the spec, but there is an obvious workaround. Nr~r r!r"rrrr!rceZdZdZdS)rz< A feature of the VOTABLE_ spec is not implemented. Nr~r r!r"rrrr!rceZdZdZdS)rzL A network or IO error occurred, but was recovered using the cache. Nr~r r!r"rrrr!rceZdZdZdS)rzO The input XML file violates the spec and there is no good workaround. Nr~r r!r"rrrr!rceZdZdZdZdS)W01aArray uses commas rather than whitespace. The VOTable spec states: If a cell contains an array or complex number, it should be encoded as multiple numbers separated by whitespace. Many VOTable files in the wild use commas as a separator instead, and ``astropy.io.votable`` can support this convention depending on the :ref:`astropy:verifying-votables` setting. ``astropy.io.votable`` always outputs files using only spaces, regardless of how they were input. **References**: `1.1 `__, `1.2 `__ z(Array uses commas rather than whitespaceNrrrrror r!r"rrs#(Br!rceZdZdZdZdZdS)W02aNonstandard XML id. XML ids must match the following regular expression:: ^[A-Za-z_][A-Za-z0-9_\.\-]*$ The VOTable 1.1 says the following: According to the XML standard, the attribute ``ID`` is a string beginning with a letter or underscore (``_``), followed by a sequence of letters, digits, or any of the punctuation characters ``.`` (dot), ``-`` (dash), ``_`` (underscore), or ``:`` (colon). However, this is in conflict with the XML standard, which says colons may not be used. VOTable 1.1's own schema does not allow a colon here. Therefore, ``astropy.io.votable`` disallows the colon. VOTable 1.2 corrects this error in the specification. **References**: `1.1 `__, `XML Names `__ z8{} attribute '{}' is invalid. Must be a standard XML idxyNrrrrrorxr r!r"rr,s&2RLLLr!rceZdZdZdZdZdS)W03a Implicitly generating an ID from a name. The VOTable 1.1 spec says the following about ``name`` vs. ``ID`` on ``FIELD`` and ``VALUE`` elements: ``ID`` and ``name`` attributes have a different role in VOTable: the ``ID`` is meant as a *unique identifier* of an element seen as a VOTable component, while the ``name`` is meant for presentation purposes, and need not to be unique throughout the VOTable document. The ``ID`` attribute is therefore required in the elements which have to be referenced, but in principle any element may have an ``ID`` attribute. ... In summary, the ``ID`` is different from the ``name`` attribute in that (a) the ``ID`` attribute is made from a restricted character set, and must be unique throughout a VOTable document whereas names are standard XML attributes and need not be unique; and (b) there should be support in the parsing software to look up references and extract the relevant element with matching ``ID``. It is further recommended in the VOTable 1.2 spec: While the ``ID`` attribute has to be unique in a VOTable document, the ``name`` attribute need not. It is however recommended, as a good practice, to assign unique names within a ``TABLE`` element. This recommendation means that, between a ``TABLE`` and its corresponding closing ``TABLE`` tag, ``name`` attributes of ``FIELD``, ``PARAM`` and optional ``GROUP`` elements should be all different. Since ``astropy.io.votable`` requires a unique identifier for each of its columns, ``ID`` is used for the column name when present. However, when ``ID`` is not present, (since it is not required by the specification) ``name`` is used instead. However, ``name`` must be cleansed by replacing invalid characters (such as whitespace) with underscores. .. note:: This warning does not indicate that the input file is invalid with respect to the VOTable specification, only that the column names in the record array may not match exactly the ``name`` attributes specified in the file. **References**: `1.1 `__, `1.2 `__ z4Implicitly generating an ID from a name '{}' -> '{}'rNrr r!r"rrJs'//bNLLLr!rceZdZdZdZdZdS)W04a The ``content-type`` attribute must use MIME content-type syntax as defined in `RFC 2046 `__. The current check for validity is somewhat over-permissive. **References**: `1.1 `__, `1.2 `__ z3content-type '{}' must be a valid MIME content typerNrr r!r"rrs&  MLLLr!rceZdZdZdZdZdS)W05zq The attribute must be a valid URI as defined in `RFC 2396 `_. z'{}' is not a valid URIrNrr r!r"rrs% 1LLLr!rceZdZdZdZdZdS)W06a This warning is emitted when a ``ucd`` attribute does not match the syntax of a `unified content descriptor `__. If the VOTable version is 1.2 or later, the UCD will also be checked to ensure it conforms to the controlled vocabulary defined by UCD1+. **References**: `1.1 `__, `1.2 `__ zInvalid UCD '{}': {})r explanationNrr r!r"rrs%  .'LLLr!rceZdZdZdZdZdS)W07aInvalid astroYear. As astro year field is a Besselian or Julian year matching the regular expression:: ^[JB]?[0-9]+([.][0-9]*)?$ Defined in this XML Schema snippet:: zInvalid astroYear in {}: '{}'rNrr r!r"rrs% 7LLLr!rceZdZdZdZdZdS)W08z To avoid local-dependent number parsing differences, ``astropy.io.votable`` may require a string or unicode string where a numeric type may make more sense. z"'{}' must be a str or bytes objectrNrr r!r"rrs% <LLLr!rceZdZdZdZdS)W09a  The VOTable specification uses the attribute name ``ID`` (with uppercase letters) to specify unique identifiers. Some VOTable-producing tools use the more standard lowercase ``id`` instead. ``astropy.io.votable`` accepts ``id`` and emits this warning if ``verify`` is ``'warn'``. **References**: `1.1 `__, `1.2 `__ zID attribute not capitalizedNrr r!r"rrs"  6r!rceZdZdZdZdZdS)W10aS The parser has encountered an element that does not exist in the specification, or appears in an invalid context. Check the file against the VOTable schema (with a tool such as `xmllint `__. If the file validates against the schema, and you still receive this warning, this may indicate a bug in ``astropy.io.votable``. **References**: `1.1 `__, `1.2 `__ zUnknown tag '{}'. IgnoringrNrr r!r"rrs%  5LLLr!rceZdZdZdZdS)W11a Earlier versions of the VOTable specification used a ``gref`` attribute on the ``LINK`` element to specify a `GLU reference `__. New files should specify a ``glu:`` protocol using the ``href`` attribute. Since ``astropy.io.votable`` does not currently support GLU references, it likewise does not automatically convert the ``gref`` attribute to the new form. **References**: `1.1 `__, `1.2 `__ z7The gref attribute on LINK is deprecated in VOTable 1.1Nrr r!r"rrs# Qr!rceZdZdZdZdZdS)W12a In order to name the columns of the Numpy record array, each ``FIELD`` element must have either an ``ID`` or ``name`` attribute to derive a name from. Strictly speaking, according to the VOTable schema, the ``name`` attribute is required. However, if ``name`` is not present by ``ID`` is, and ``verify`` is not ``'exception'``, ``astropy.io.votable`` will continue without a ``name`` defined. **References**: `1.1 `__, `1.2 `__ z@'{}' element must have at least one of 'ID' or 'name' attributesrNrr r!r"rrs*   KLLLr!rceZdZdZdZdZdS)W13aInvalid VOTable datatype. Some VOTable files in the wild use non-standard datatype names. These are mapped to standard ones using the following mapping:: string -> char unicodeString -> unicodeChar int16 -> short int32 -> int int64 -> long float32 -> float float64 -> double unsignedInt -> long unsignedShort -> int To add more datatype mappings during parsing, use the ``datatype_mapping`` keyword to `astropy.io.votable.parse`. **References**: `1.1 `__, `1.2 `__ z4'{}' is not a valid VOTable datatype, should be '{}'rNrr r!r"rrs&0NLLLr!rceZdZdZdZdZdS)W15a The ``name`` attribute is required on every ``FIELD`` element. However, many VOTable files in the wild omit it and provide only an ``ID`` instead. In this case, when ``verify`` is not ``'exception'`` ``astropy.io.votable`` will copy the ``name`` attribute to a new ``ID`` attribute. **References**: `1.1 `__, `1.2 `__ z,{} element missing required 'name' attributerNrr r!r"rr=s&  FLLLr!rceZdZdZdZdZdS)W17a A ``DESCRIPTION`` element can only appear once within its parent element. According to the schema, it may only occur once (`1.1 `__, `1.2 `__) However, it is a `proposed extension `__ to VOTable 1.2. z5{} element contains more than one DESCRIPTION elementrNrr r!r"rrRs&  OLLLr!rceZdZdZdZdZdS)W18aB The number of rows explicitly specified in the ``nrows`` attribute does not match the actual number of rows (``TR`` elements) present in the ``TABLE``. This may indicate truncation of the file, or an internal error in the tool that produced it. If ``verify`` is not ``'exception'``, parsing will proceed, with the loss of some performance. **References:** `1.1 `__, `1.2 `__ z4TABLE specified nrows={}, but table contains {} rowsrNrr r!r"rres&  NLLLr!rceZdZdZdZdS)W19z The column fields as defined using ``FIELD`` elements do not match those in the headers of the embedded FITS file. If ``verify`` is not ``'exception'``, the embedded FITS file will take precedence. zNThe fields defined in the VOTable do not match those in the embedded FITS fileNrr r!r"rrws$ r!rceZdZdZdZdZdS)W20z If no version number is explicitly given in the VOTable file, the parser assumes it is written to the VOTable 1.1 specification. z1No version number specified in file. Assuming {})z1.1Nrr r!r"rrs& KLLLr!rceZdZdZdZdZdS)W21z Unknown issues may arise using ``astropy.io.votable`` with VOTable files from a version other than 1.1, 1.2, 1.3, or 1.4. z^astropy.io.votable is designed for VOTable version 1.1, 1.2, 1.3, and 1.4, but this file is {}rNrr r!r"rrs)  (LLLr!rceZdZdZdZdS)W22a Version 1.0 of the VOTable specification used the ``DEFINITIONS`` element to define coordinate systems. Version 1.1 now uses ``COOSYS`` elements throughout the document. **References:** `1.1 `__, `1.2 `__ z?The DEFINITIONS element is deprecated in VOTable 1.1. IgnoringNrr r!r"rrs#  Yr!rceZdZdZdZdZdS)W23z Raised when the VO service database can not be updated (possibly due to a network outage). This is only a warning, since an older and possible out-of-date VO service database was available locally. z-Unable to update service information for '{}'rNrr r!r"rrs&GLLLr!rceZdZdZdZdS)W24a  The VO catalog database retrieved from the www is designed for a newer version of ``astropy.io.votable``. This may cause problems or limited features performing service queries. Consider upgrading ``astropy.io.votable`` to the latest version. zDThe VO catalog database is for a later version of astropy.io.votableNrr r!r"rrs% Or!rceZdZdZdZdZdS)W25z A VO service query failed due to a network error or malformed arguments. Another alternative service may be attempted. If all services fail, an exception will be raised. z'{}' failed with: {})servicez...Nrr r!r"rrs% .%LLLr!rceZdZdZdZdZdS)W26z The given element was not supported inside of the given element until the specified VOTable version, however the version declared in the file is for an earlier version. These attributes may not be written out to the file. z$'{}' inside '{}' added in VOTable {})childparentX.XNrr r!r"rrs%>-LLLr!rceZdZdZdZdS)W27ad The ``COOSYS`` element was deprecated in VOTABLE version 1.2 in favor of a reference to the Space-Time Coordinate (STC) data model (see `utype `__ and the IVOA note `referencing STC in VOTable `__. z COOSYS deprecated in VOTable 1.2Nrr r!r"rrs":r!rceZdZdZdZdZdS)W28z The given attribute was not supported on the given element until the specified VOTable version, however the version declared in the file is for an earlier version. These attributes may not be written out to the file. z '{}' on '{}' added in VOTable {}) attributerOrNrr r!r"rrs%:2LLLr!rceZdZdZdZdZdS)W29aY Some VOTable files specify their version number in the form "v1.0", when the only supported forms in the spec are "1.0". **References**: `1.1 `__, `1.2 `__ z+Version specified in non-standard form '{}')zv1.0Nrr r!r"rrs&ELLLr!rceZdZdZdZdZdS)W30a Some VOTable files write missing floating-point values in non-standard ways, such as "null" and "-". If ``verify`` is not ``'exception'``, any non-standard floating-point literals are treated as missing values. **References**: `1.1 `__, `1.2 `__ z3Invalid literal for float '{}'. Treating as empty.rNrr r!r"rrs&  MLLLr!rceZdZdZdZdS)W31a Since NaN's can not be represented in integer fields directly, a null value must be specified in the FIELD descriptor to support reading NaN's from the tabledata. **References**: `1.1 `__, `1.2 `__ z=NaN given in an integral field without a specified null valueNrr r!r"rrs#  Wr!rceZdZdZdZdZdS)W32a Each field in a table must have a unique ID. If two or more fields have the same ID, some will be renamed to ensure that all IDs are unique. From the VOTable 1.2 spec: The ``ID`` and ``ref`` attributes are defined as XML types ``ID`` and ``IDREF`` respectively. This means that the contents of ``ID`` is an identifier which must be unique throughout a VOTable document, and that the contents of the ``ref`` attribute represents a reference to an identifier which must exist in the VOTable document. **References**: `1.1 `__, `1.2 `__ z6Duplicate ID '{}' renamed to '{}' to ensure uniquenessrx_2Nrr r!r"rr!s&(PLLLr!rceZdZdZdZdZdS)W33a~ Each field in a table must have a unique name. If two or more fields have the same name, some will be renamed to ensure that all names are unique. **References**: `1.1 `__, `1.2 `__ z5Column name '{}' renamed to '{}' to ensure uniquenessrNrr r!r"rr:s&  OLLLr!rceZdZdZdZdZdS)W34z The attribute requires the value to be a valid XML token, as defined by `XML 1.0 `__. z+'{}' is an invalid token for attribute '{}'rNrr r!r"rrJs& ELLLr!rceZdZdZdZdZdS)W35a- The ``name`` and ``value`` attributes are required on all ``INFO`` elements. **References:** `1.1 `__, `1.2 `__ z)'{}' attribute required for INFO elementsrNrr r!r"rrUs&CLLLr!rceZdZdZdZdZdS)W36aF If the field specifies a ``null`` value, that value must conform to the given ``datatype``. **References:** `1.1 `__, `1.2 `__ z;null value '{}' does not match field datatype, setting to 0rNrr r!r"rrds&ULLLr!rceZdZdZdZdZdS)W37ao The 3 datatypes defined in the VOTable specification and supported by ``astropy.io.votable`` are ``TABLEDATA``, ``BINARY`` and ``FITS``. **References:** `1.1 `__, `1.2 `__ zUnsupported data format '{}'rNrr r!r"rrss%6LLLr!rceZdZdZdZdZdS)W38zg The only encoding for local binary data supported by the VOTable specification is base64. z3Inline binary data must be base64 encoded, got '{}'rNrr r!r"rrs& MLLLr!rceZdZdZdZdS)W39aU Bit values do not support masking. This warning is raised upon setting masked data in a bit column. **References**: `1.1 `__, `1.2 `__ zBit values can not be maskedNrr r!r"rrs"6r!rceZdZdZdZdS)W40a This is a terrible hack to support Simple Image Access Protocol results from `NOIRLab Astro Data Archive `__. It creates a field for the coordinate projection type of type "double", which actually contains character data. We have to hack the field to store character data, or we can't read it in. A warning will be raised when this happens. z'cprojection' datatype repairedNrr r!r"rrs"9r!rceZdZdZdZdZdS)W41a An XML namespace was specified on the ``VOTABLE`` element, but the namespace does not match what is expected for a ``VOTABLE`` file. The ``VOTABLE`` namespace is:: http://www.ivoa.net/xml/VOTable/vX.X where "X.X" is the version number. Some files in the wild set the namespace to the location of the VOTable schema, which is not correct and will not pass some validating parsers. zIAn XML namespace is specified, but is incorrect. Expected '{}', got '{}'rNrr r!r"rrs*   TLLLr!rceZdZdZdZdS)W42zThe root element should specify a namespace. The ``VOTABLE`` namespace is:: http://www.ivoa.net/xml/VOTable/vX.X where "X.X" is the version number. zNo XML namespace specifiedNrr r!r"rrs"4r!rceZdZdZdZdZdS)W43zReferenced elements should be defined before referees. From the VOTable 1.2 spec: In VOTable1.2, it is further recommended to place the ID attribute prior to referencing it whenever possible. z.{} ref='{}' which has not already been defined)rOrNrr r!r"rrs&H#LLLr!rceZdZdZdZdZdS)W44a ``VALUES`` elements that reference another element should not have their own content. From the VOTable 1.2 spec: The ``ref`` attribute of a ``VALUES`` element can be used to avoid a repetition of the domain definition, by referring to a previously defined ``VALUES`` element having the referenced ``ID`` attribute. When specified, the ``ref`` attribute defines completely the domain without any other element or attribute, as e.g. ```` z4VALUES element with ref attribute has content ('{}'))rONrr r!r"rrs&  NLLLr!rceZdZdZdZdZdS)W45aInvalid content-role attribute. The ``content-role`` attribute on the ``LINK`` element must be one of the following:: query, hints, doc, location And in VOTable 1.3, additionally:: type **References**: `1.1 `__, `1.2 `__ `1.3 `__ z#content-role attribute '{}' invalidrNrr r!r"rrs%&=LLLr!rceZdZdZdZdZdS)W46zZ The given char or unicode string is too long for the specified field length. z/{} value is too long for specified length of {})zchar or unicoderNrr r!r"rrs& I+LLLr!rceZdZdZdZdS)W47z If no arraysize is specified on a char field, the default of '1' is implied, but this is rarely what is intended. z$Missing arraysize indicates length 1Nrr r!r"rr " >r!rceZdZdZdZdZdS)rNz< The attribute is not defined in the specification. zUnknown attribute '{}' on {})rrONrr r!r"rNrNs%6+LLLr!rNceZdZdZdZdS)W49z Prior to VOTable 1.3, the empty cell was illegal for integer fields. If a "null" value was specified for the cell, it will be used for the value, otherwise, 0 will be used. z&Empty cell illegal for integer fields.Nrr r!r"rrs#@r!rceZdZdZdZdZdS)W50a Invalid unit string as defined in the `Units in the VO, Version 1.0 `_ (VOTable version >= 1.4) or `Standards for Astronomical Catalogues, Version 2.0 `_ (version < 1.4). Consider passing an explicit ``unit_format`` parameter if the units in this file conform to another specification. zInvalid unit string '{}'rNrr r!r"rr*s%2LLLr!rceZdZdZdZdZdS)W51zF The integer value is out of range for the size of the field. z1Value '{}' is out of range for a {} integer field)rzn-bitNrr r!r"rr9s&K!LLLr!rceZdZdZdZdZdS)W52z The BINARY2 format was introduced in VOTable 1.3. It should not be present in files marked as an earlier version. z[The BINARY2 format was introduced in VOTable 1.3, but this file is declared as version '{}')z1.2Nrr r!r"rrB)  0LLLr!rceZdZdZdZdZdS)W53zI The VOTABLE element must contain at least one RESOURCE element. z;VOTABLE element must contain at least one RESOURCE element.r Nrr r!r"rrOs&ULLLr!rceZdZdZdZdZdS)W54z The TIMESYS element was introduced in VOTable 1.4. It should not be present in files marked as an earlier version. z\The TIMESYS element was introduced in VOTable 1.4, but this file is declared as version '{}')z1.3Nrr r!r"rrXrr!rceZdZdZdZdZdS)W55z When non-ASCII characters are detected when reading a TABLEDATA value for a FIELD with ``datatype="char"``, we can issue this warning. z@FIELD ({}) has datatype="char" but contains non-ASCII value ({})rBrBNrr r!r"rres* KLLLr!rceZdZdZdZdZdS)E01aInvalid size specifier for a field. The size specifier for a ``char`` or ``unicode`` field must be only a number followed, optionally, by an asterisk. Multi-dimensional size specifiers are not supported for these datatypes. Strings, which are defined as a set of characters, can be represented in VOTable as a fixed- or variable-length array of characters:: A 1D array of strings can be represented as a 2D array of characters, but given the logic above, it is possible to define a variable-length array of fixed-length strings, but not a fixed-length array of variable-length strings. z:Invalid size specifier '{}' for a {} field (in field '{}'))rz char/unicoderNrr r!r"rrrs&&T-LLLr!rceZdZdZdZdZdS)E02zIncorrect number of elements in array. The number of array elements in the data does not match that specified in the FIELD specifier. zFIncorrect number of elements in array. Expected multiple of {}, got {}rNrr r!r"rrs* QLLLr!rceZdZdZdZdZdS)E03a%Complex numbers should be two values separated by whitespace. **References**: `1.1 `__, `1.2 `__ z''{}' does not parse as a complex numberrNrr r!r"rrs&ALLLr!rceZdZdZdZdZdS)E04aA ``bit`` array should be a string of '0's and '1's. **References**: `1.1 `__, `1.2 `__ zInvalid bit value '{}'rNrr r!r"rrs%0LLLr!rceZdZdZdZdZdS)E05aInvalid boolean value. A ``boolean`` value should be one of the following strings (case insensitive) in the ``TABLEDATA`` format:: 'TRUE', 'FALSE', '1', '0', 'T', 'F', '\0', ' ', '?' and in ``BINARY`` format:: 'T', 'F', '1', '0', '\0', ' ', '?' **References**: `1.1 `__, `1.2 `__ zInvalid boolean value '{}'rNrr r!r"rrs%"4LLLr!rceZdZdZdZdZdS)E06aUnknown datatype on a field. The supported datatypes are:: double, float, bit, boolean, unsignedByte, short, int, long, floatComplex, doubleComplex, char, unicodeChar The following non-standard aliases are also supported, but in these case :ref:`W13 ` will be raised:: string -> char unicodeString -> unicodeChar int16 -> short int32 -> int int64 -> long float32 -> float float64 -> double unsignedInt -> long unsignedShort -> int To add more datatype mappings during parsing, use the ``datatype_mapping`` keyword to `astropy.io.votable.parse`. **References**: `1.1 `__, `1.2 `__ z#Unknown datatype '{}' on field '{}'rNrr r!r"r r s%:=LLLr!r ceZdZdZdZdZdS)E08aC The ``type`` attribute on the ``VALUES`` element must be either ``legal`` or ``actual``. **References**: `1.1 `__, `1.2 `__ z-type must be 'legal' or 'actual', but is '{}'rNrr r!r"r r s&GLLLr!r ceZdZdZdZdZdS)E09a? The ``MIN``, ``MAX`` and ``OPTION`` elements must always have a ``value`` attribute. **References**: `1.1 `__, `1.2 `__ z '{}' must have a value attributerNrr r!r"r r s%:LLLr!r ceZdZdZdZdZdS)E10aG From VOTable 1.1 and later, ``FIELD`` and ``PARAM`` elements must have a ``datatype`` field. **References**: `1.1 `__, `1.2 `__ z2'datatype' attribute required on all '{}' elements)FIELDNrr r!r"rr s&LLLLr!rceZdZdZdZdZdS)E11a The precision attribute is meant to express the number of significant digits, either as a number of decimal places (e.g. ``precision="F2"`` or equivalently ``precision="2"`` to express 2 significant figures after the decimal point), or as a number of significant figures (e.g. ``precision="E5"`` indicates a relative precision of 10-5). It is validated using the following regular expression:: [EF]?[1-9][0-9]* **References**: `1.1 `__, `1.2 `__ zprecision '{}' is invalidrNrr r!r"rrs%"3LLLr!rceZdZdZdZdZdS)E12ao The width attribute is meant to indicate to the application the number of characters to be used for input or output of the quantity. **References**: `1.1 `__, `1.2 `__ z*width must be a positive integer, got '{}'rNrr r!r"rr/s&  DLLLr!rceZdZdZdZdZdS)E13uInvalid arraysize attribute. From the VOTable 1.2 spec: A table cell can contain an array of a given primitive type, with a fixed or variable number of elements; the array may even be multidimensional. For instance, the position of a point in a 3D space can be defined by the following:: and each cell corresponding to that definition must contain exactly 3 numbers. An asterisk (\*) may be appended to indicate a variable number of elements in the array, as in:: where it is specified that each cell corresponding to that definition contains 0 to 100 integer numbers. The number may be omitted to specify an unbounded array (in practice up to =~2×10⁹ elements). A table cell can also contain a multidimensional array of a given primitive type. This is specified by a sequence of dimensions separated by the ``x`` character, with the first dimension changing fastest; as in the case of a simple array, the last dimension may be variable in length. As an example, the following definition declares a table cell which may contain a set of up to 10 images, each of 64×64 bytes:: **References**: `1.1 `__, `1.2 `__ z Invalid arraysize attribute '{}'rNrr r!r"rr?s&$$L:LLLr!rceZdZdZdZdS)E14a All ``PARAM`` elements must have a ``value`` attribute. **References**: `1.1 `__, `1.2 `__ z2value attribute is required for all PARAM elementsNrr r!r"rrjs#Lr!rceZdZdZdZdS)E15zAll ``COOSYS`` elements must have an ``ID`` attribute. Note that the VOTable 1.1 specification says this attribute is optional, but its corresponding schema indicates it is required. In VOTable 1.2, the ``COOSYS`` element is deprecated. z0ID attribute is required for all COOSYS elementsNrr r!r"rrws#Jr!rceZdZdZdZdZdS)E16ajIncorrect ``system`` attribute on COOSYS element. The ``system`` attribute must be one of the following:: 'eq_FK4', 'eq_FK5', 'ICRS', 'ecl_FK4', 'ecl_FK5', 'galactic', 'supergalactic', 'xy', 'barycentric', 'geo_app' **References**: `1.1 `__ zInvalid system attribute '{}'rNrr r!r"rrs%  7LLLr!rceZdZdZdZdS)E17a  ``extnum`` attribute must be a positive integer. **References**: `1.1 `__, `1.2 `__ z!extnum must be a positive integerNrr r!r"rrs";r!rceZdZdZdZdZdS)E18a7 The ``type`` attribute of the ``RESOURCE`` element must be one of "results" or "meta". **References**: `1.1 `__, `1.2 `__ z*type must be 'results' or 'meta', not '{}'rNrr r!r"r r s&DLLLr!r ceZdZdZdZdS)E19zg Raised either when the file doesn't appear to be XML, or the root element is not VOTABLE. z$File does not appear to be a VOTABLENrr r!r"r"r"rr!r"ceZdZdZdZdZdS)E20zd The table had only *x* fields defined, but the data itself has more columns than that. z9Data has more columns than are defined in the header ({})rNrr r!r"r$r$s& SLLLr!r$ceZdZdZdZdZdS)E21zY The table had *x* fields defined, but the data itself has only *y* columns. z?Data has fewer columns ({}) than are defined in the header ({})rNrr r!r"r&r&s& YLLLr!r&ceZdZdZdZdS)E22zA All ``TIMESYS`` elements must have an ``ID`` attribute. z1ID attribute is required for all TIMESYS elementsNrr r!r"r(r(s#Kr!r(ceZdZdZdZdZdS)E23a} The ``timeorigin`` attribute on the ``TIMESYS`` element must be either a floating point literal specifying a valid Julian Date, or, for convenience, the string "MJD-origin" (standing for 2400000.5) or the string "JD-origin" (standing for 0). **References**: `1.4 `__ z!Invalid timeorigin attribute '{}'rNrr r!r"r*r*s%;LLLr!r*ceZdZdZdZdZdS)E24z Non-ASCII unicode values should not be written when the FIELD ``datatype="char"``, and cannot be written in BINARY or BINARY2 serialization. zMAttempt to write non-ASCII value ({}) to FIELD ({}) which has datatype="char"rNrr r!r"r,r,s* XLLLr!r,ceZdZdZdZdS)E25z_ A VOTable cannot have a DATA section without any defined FIELD; DATA will be ignored. z4No FIELDs are defined; DATA section will be ignored.Nrr r!r"r.r.s#Nr!r.cg}tD]4\}}tj|dz|r|||f5||S)Nz[0-9]{2})globalsitemsrerjappendsort)prefixclasseskeyvals r""_get_warning_and_exception_classesr9sjGIIOO%%''S 8FZ' - - ' NNC: & & & LLNNN Nr!c>d}|d}|d}||dS)Nct|}tj}|D]3\}}|d|d|jd|}t |ts|d}|||d|dt|z|d|j }t |ts|d}|t||d5| S)Nz.. _z: r(r^ ~z ) r9ioStringIOwriterrzrfrErgrHrrgetvalue)r5r6outr+ryrtdocs r" generate_setz'_build_doc_string..generate_sets@4V<<kmm  ID# II(T((( ) ) )\;;S%7%7%9%9;;Cc3'' *jj)) IIcNNN IIdOOO IIcCHHn % % % IIf   +Cc3'' *jj)) IIfSkk " " " IIf    ||~~r!rTE)warnings exceptionsr )rDrFrGs r"_build_doc_stringrHs?,|C  Hc""J ; ;;r!cg|] }|d Srr .0rs r" rM FFF!FFFr!rTcg|] }|d SrJr rKs r"rMrM!rNr!rEr{)r.)Nr NNr')r NN)NNrB)r NNr')urr>r2textwraprrFrastropyrrastropy.utils.exceptionsr__all__ConfigNamespacerrr-r:r r r r r compiler_rr SyntaxWarningrrrRuntimeWarningrrerrrrrrrrrrrrrrrrrrrrrr FutureWarningrrrrrrrrrrrrrrrrrrrrrrrrrNrrrrrrrrrrrrr r r rrrrrrrrr r"r$r&r(r*r,r.r9rHrpextendr r!r"rZs@ %%%%%%333333   &     7 "    tvv>>>> 1 1 1 1UVMMMM(----$ H H H H?AQRRRR rz0 '''T$$$$$$$$B9m M 9m  > y* BBBBB BBB0 <33333 333l " ((((( (((( *         66666 666" &QQQQQ QQQ( * @ * & $                    Y Y Y Y Y  Y Y Y     )        )]   &&&&&)&&& . . . . .  . . . : : : : :  : : : 3 3 3 3 3  3 3 3                   W W W W W  W W W        2                                        6 6 6 6 6  6 6 6 9 9 9 9 9  9 9 9 , 4 4 4 4 4  4 4 4 $ $ $ $ $  $ $ $        &)Z0,,,,, ,,,>>>>> >>>,,,,, ,,, @ @ @ @ @  @ @ @         """"" """                            .....)Z...0     )Z        )Z        )Z   )Z,)ZJ     )Z        )Z        )Z   )Z,     )Z    ((((()Z(((V L L L L L)Z L L L J J J J J)Z J J J          ; ; ; ; ;)Z ; ; ;     )Z   >>>>>)Z>>> )ZKKKKK)ZKKK              )Z   NNNNN NNN<<<: gn33002233GFF@@EEFFFGGGFF@@EEFFFGGGGGr!