Skip to content
Snippets Groups Projects
Select Git revision
  • alert-improvements
  • api-v2
  • bug-fixes
  • catalog-dev
  • er16-and-split-O4
  • fast-get-objects-for-user
  • fix_likelihood
  • fs-fix
  • glitchdb-dev
  • gracedb-2.21.3-1
  • gracedb-2.21.8-1
  • gracedb-2.22.0-1
  • gwtc-labels
  • histogram
  • hw-inj
  • inheritance-v2
  • master default protected
  • nan-be-gone
  • new_event_superevent_types
  • no-massgap-voevent
  • gracedb-2.31.0
  • gracedb-2.30.0-1
  • gracedb-2.30.0
  • gracedb-2.29.0
  • gracedb-2.28.2
  • gracedb-2.28.1
  • gracedb-2.28.0
  • gracedb-2.27.2
  • gracedb-2.27.1
  • gracedb-2.27.0
  • gracedb-2.26.0
  • gracedb-2.25.0
  • gracedb-2.24.0
  • gracedb-2.23.2
  • gracedb-2.23.1
  • gracedb-2.23.0
  • gracedb-2.22.0-1
  • gracedb-2.22.0
  • gracedb-2.21.8
  • gracedb-2.21.7
40 results
You can move around the graph by using the arrow keys.
Created with Raphaël 2.2.026Sep2524232219161510426Aug25222120191814121176530Jul2822181717Mar4317Feb14105431Jan292625242322191817718Nov1523Sep9429Aug28830Jul262524232219181715141211109328Jun272524212019181413121130May222163230Apr1918171129Mar2827138425Feb232220151411531Jan241816151410987419Dec131175430Nov291615147131Oct302418Sep25Jul201918171613121195228Jun2726252120191411876431May301724Apr9Feb86432130Jan272624231712109620Dec1914530Nov520Oct30Aug261816229Jul272120191514230Jun24216Apr151412530Mar24Feb23Jan1514126522Dec1918171615118742125Nov1917161311109529Oct2717Aug13Fixed make_histogram command so that you get one histogram per pipeline, instead of one histogram per analysisType. This will mix HighMass and LowMass events, so we may want to split on search, where search is available. But I don't think it's that criticial since we aren't using these histograms much.I made analysisType go away in a few places inside api.py. This was suspiciously easy.Fixed cli view to return pipeline,search columns instead of analysisType. Nobody should be using this thang though.'Fixed' feeds in order not to refer to analysisType. Instead of atype, feeds allows you to specify a pipeline. But not a search.Fixed buildVOEvent for pipeline,searchFixed guided search (EventSearchForm and oldsearch) to use Pipeline and Search instead of analysisTypeChanged event view template selector. Also reduced number of event detail sub-templates to 3. The extra ones were not necessary.Fixed flexigrid response.Added comment in reports.pyI think I fixed the query parser to use pipeline and search rather than analysisType, but I havent' fixed the documentation yet.removed analysis type from alert.py, sending xmpp alert to new node names with group_pipeline_search.Finished removing AnalysisType from userprofile app.I guess there was a final schema migration that Brian had left undone for the userprofile app. Here it is.Removed analysis type from admin interface, added pipeline and search.Fixed getByGraceid and graceid for the new distinguishing fields.Removed analysisType to event creator and handle_uploaded_data, replaced with Pipeline, SearchAdded new fields to event creation form.removed default value for Event.pipelineRemoved analysisType field from events.Data migration to assign pipeline and search for existing events.Added CWB for migrating old events.Added GRB search.Added Test search to initial searches fixture.Using special database for the event_namespace branch.Added new fields on event model. Default pipline pk=1.Fixed null->blank on some textual fields, added more pipelines.Fixtures and migrations for Pipelines and Searches.Changed length of pipeline and search names to 100 chars.Created Pipeline and Search objects, along with schema migration.Merge branch 'cleanup' into guardianMerge branch 'master' into cleanupAdded test to make sure that anybody can create an event in the 'Test' group.Added remaining unit tests for event creation and permission object creation.Completed tests of safe methods.Fixed type of in iDQ user migration.Data migration for idq users at LLO and HAN.migration file recreatedMust create guardian GroupObjectPermission objects and auth.Permission objects on the fly in test setUp, *because* django creates content type id's in an unpredictable manner when it runs syncdb for the first time. Since the permissions infrastructure depends on these content type ids, you can't use dumped objects for testing.Changed test_perms fixtures so that you could hand-pick the event id's, if desired. Ugh.Changed test_perms fixtures so that you could hand-pick the event id's, if desired.