GraceDB Server issueshttps://git.ligo.org/computing/gracedb/server/-/issues2022-08-03T18:49:25Zhttps://git.ligo.org/computing/gracedb/server/-/issues/63Fix the way instruments are stored for events2022-08-03T18:49:25ZTanner PrestegardFix the way instruments are stored for eventsCreated August 16, 2017. Copied from redmine (https://bugs.ligo.org/redmine/issues/5694)
Instruments are currently associated with events by a string like "H1,L1" or "H1,L1,V1". This is an ineffective way of doing it and prevents effici...Created August 16, 2017. Copied from redmine (https://bugs.ligo.org/redmine/issues/5694)
Instruments are currently associated with events by a string like "H1,L1" or "H1,L1,V1". This is an ineffective way of doing it and prevents efficient instrument-based queries.
We should create an instruments model and just have a many-to-many relationship with events (may need to create a go-between like "labelling").
I think there is also an 'ifos' variable: we should resolve the redundancy issue if that's the case.Backloghttps://git.ligo.org/computing/gracedb/server/-/issues/25Allow negative searches2022-08-03T18:19:12ZTanner PrestegardAllow negative searchesStarted on June 3, 2015 by Branson. Copied from redmine (https://bugs.ligo.org/redmine/issues/2175)
> On Jun 3, 2015, at 10:42 AM, Salvatore Vitale <salvatore.vitale@ligo.mit.edu> wrote:
>
> Hi Branson,
>
> Is there a way to perform a...Started on June 3, 2015 by Branson. Copied from redmine (https://bugs.ligo.org/redmine/issues/2175)
> On Jun 3, 2015, at 10:42 AM, Salvatore Vitale <salvatore.vitale@ligo.mit.edu> wrote:
>
> Hi Branson,
>
> Is there a way to perform a negative query on graceDB. E.g. I tried
>
> search: !MDC pipeline: cwb
>
> but that doesn't work. I tried a few other syntaxes (not, !=, <>) but none seems to work
>
> Thanks,
> salvoBackloghttps://git.ligo.org/computing/gracedb/server/-/issues/24Search for hardware injection by id H208670 misinterpreted2022-08-03T18:18:19ZTanner PrestegardSearch for hardware injection by id H208670 misinterpretedStarted on February 2, 2016 by Branson. Copied from redmine (https://bugs.ligo.org/redmine/issues/3543)
The query parser strips off the 'H2' and interprets it as an instrument search. The remaining '08670' is interpreted as an integer, ...Started on February 2, 2016 by Branson. Copied from redmine (https://bugs.ligo.org/redmine/issues/3543)
The query parser strips off the 'H2' and interprets it as an instrument search. The remaining '08670' is interpreted as an integer, and therefore a gpstime query.Backloghttps://git.ligo.org/computing/gracedb/server/-/issues/23GraceDB search suggestions2022-08-03T18:17:49ZTanner PrestegardGraceDB search suggestionsFrom Brian O'Reilly, started on January 24, 2017. Copied from redmine (https://bugs.ligo.org/redmine/issues/5052)
The search help does not reflect the actual functionality of the search. It may be that the search functions as expected a...From Brian O'Reilly, started on January 24, 2017. Copied from redmine (https://bugs.ligo.org/redmine/issues/5052)
The search help does not reflect the actual functionality of the search. It may be that the search functions as expected and one cal only use relational operators in restricted ways, but this isn't clear. Also the layout of the search results returned from the "Search" tab is different from what you see if you do a search from the "Latest" tab.
For example, "far<1e-6 ~INJ" works but the help seems to indicate that the syntax should be "far<1e-6 & ~INJ"
"H1OK | L1OK & ~INJ & ~DQV" works but there doesn't seem to be any way to add a FAR cut, e.g. "far<1e-6", to this
query.
You can see all results from a particular pipeline removing injections and adding a FAR cut: "cwb far<1e-7 ~inj", but from the help one expects the syntax to be "cwb & far<1e-7 & ~inj"
It would be nice to be able to remove a given pipeline from the search results. "~cwb" for example does not work.Backloghttps://git.ligo.org/computing/gracedb/server/-/issues/22Overhaul of search feature2022-08-03T18:16:59ZTanner PrestegardOverhaul of search featureStarted on April 15, 2017. Copied from redmine (https://bugs.ligo.org/redmine/issues/5432)
The search feature really needs to be redone. There are several requests for new features (#1337, #2175, #3543, #5052) and the code (gracedb/quer...Started on April 15, 2017. Copied from redmine (https://bugs.ligo.org/redmine/issues/5432)
The search feature really needs to be redone. There are several requests for new features (#1337, #2175, #3543, #5052) and the code (gracedb/query.py) is really clunky. There is also a serious lack of consistency regarding when logical operators, quotes, keywords, etc. can/should be used.
Ideas from Patrick:
define a "language" for the search and STICK TO IT. Can get ideas from Google, other search syntaxes.
get feedback from users on any commonly used searches (primarily by automated systems) in order to make sure they don't break with the update (may have to break them, we'll see)
could be similar to natural language processing
expand search capabilities beyond what we have now, including the ability to search by mass, other parameters
improve overall architecture
think about design, understand uses, make a ~1 page write-up describing your planBackloghttps://git.ligo.org/computing/gracedb/server/-/issues/21Introduce type-ahead- or tab-completion-like features to the GraceDB search2022-08-03T18:14:45ZTanner PrestegardIntroduce type-ahead- or tab-completion-like features to the GraceDB searchStarted on May 9, 2014 by Branson. Copied from redmine (https://bugs.ligo.org/redmine/issues/1337)
From a conversation with Fan, Erik, and Patrick on May 8, 2014.
Fan suggested a type-ahead feature, as in Google search. You start typin...Started on May 9, 2014 by Branson. Copied from redmine (https://bugs.ligo.org/redmine/issues/1337)
From a conversation with Fan, Erik, and Patrick on May 8, 2014.
Fan suggested a type-ahead feature, as in Google search. You start typing, and the event list is narrowed down as you go, before your very eyes.
I pointed out that this might be difficult, as we can't load huge numbers of events into a datastore in order to facilitate this.
Patrick suggested that even keyword completion feature would be really useful. If you start typing 'Te...', GraceDB could fill in 'Test' by looking at her lexicon of keywords.Backlog