Open wheeyeon opened 5 years ago
Right, this is almost certainly because of the comma in the molecule name. This is likely a real bug. We probably need to add a hack that replaces commas in the molecule name with, say, underscores. You can look at the raw return by looking at the result from query_lines_async
and see if you can figure out how to parse the result.
Oh, I even wonder whether the ascii reader should be more clever and recognize that the it should ignore the comma inside quotation marks. If it should, then it's an upstream astropy issue. @taldcroft - what do you think?
It seems like the problem is the colon in certain values of "Resolved QNs". Checking from the splatalogue site shows that "Resolved QNs" for 2,4-Pentadiynylidyne is "J-1/2: 2 - 1, Ω = 1/2, f". It seems that this was split into 'J-1/2' and '2-1,Ω=1/2,f'. Querying for 2,4-Pentadiynylidyne at frequencies where there isn't a colon works without error. Searching for other molecules with a comma in the molecule name seems to work fine as well.
Hello, I am trying to use Splatalogue.query_lines() to get line intensity data for a certain frequency range. When running the following code, I run into an error as shown below. It seems that the error only happens when the query involves '2,4-Pentadiynylidyne'. I wonder if there is a way to fix this as I would like to eventually write a code to calculate the spectrum for an arbitrary frequency range.
astropy : 3.1 astroquery : 0.3.9