sherpa is hosted by Hepforge, IPPP Durham
close Warning:
  • Error with navigation contributor "BrowserModule"
  • Failed to sync with repository "(default)": instance.__dict__ not accessible in restricted mode; repository information may be out of date. Look in the Trac log for more information including mitigation strategies.

TicketQuery Wiki Macro

The TicketQuery macro lets you display ticket information anywhere that accepts WikiFormatting. The query language used by the [[TicketQuery]] macro is described in the TracQuery page.

Usage

[[TicketQuery]]

Wiki macro listing tickets that match certain criteria.

This macro accepts a comma-separated list of keyed parameters, in the form "key=value".

If the key is the name of a field, the value must use the syntax of a filter specifier as defined in TracQuery#QueryLanguage. Note that this is not the same as the simplified URL syntax used for query: links starting with a ? character. Commas (,) can be included in field values by escaping them with a backslash (\).

Groups of field constraints to be OR-ed together can be separated by a literal or argument.

In addition to filters, several other named parameters can be used to control how the results are presented. All of them are optional.

The format parameter determines how the list of tickets is presented:

  • list -- the default presentation is to list the ticket ID next to the summary, with each ticket on a separate line.
  • compact -- the tickets are presented as a comma-separated list of ticket IDs.
  • count -- only the count of matching tickets is displayed
  • rawcount -- only the count of matching tickets is displayed, not even with a link to the corresponding query (since 1.1.1)
  • table -- a view similar to the custom query view (but without the controls)
  • progress -- a view similar to the milestone progress bars

The max parameter can be used to limit the number of tickets shown (defaults to 0, i.e. no maximum).

The order parameter sets the field used for ordering tickets (defaults to id).

The desc parameter indicates whether the order of the tickets should be reversed (defaults to false).

The group parameter sets the field used for grouping tickets (defaults to not being set).

The groupdesc parameter indicates whether the natural display order of the groups should be reversed (defaults to false).

The verbose parameter can be set to a true value in order to get the description for the listed tickets. For table format only. deprecated in favor of the rows parameter

The rows parameter can be used to specify which field(s) should be viewed as a row, e.g. rows=description|summary

The col parameter can be used to specify which fields should be viewed as columns. For table format only.

For compatibility with Trac 0.10, if there's a last positional parameter given to the macro, it will be used to specify the format. Also, using "&" as a field separator still works (except for order) but is deprecated.

Examples

Example Result Macro
Number of Triage tickets: 8 [[TicketQuery(status=new&milestone=,count)]]
Number of new tickets: 40 [[TicketQuery(status=new,count)]]
Number of reopened tickets: 1 [[TicketQuery(status=reopened,count)]]
Number of assigned tickets: 3 [[TicketQuery(status=assigned,count)]]
Number of invalid tickets: 39 [[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets: 15 [[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets: 9 [[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets: 37 [[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets: 204 [[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset): 8 [[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets: 348 [[TicketQuery(count)]]
Number of tickets reported or owned by current user: 8 [[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
Number of tickets created this month: 0 [[TicketQuery(created=thismonth..,count)]]
Number of closed Firefox tickets: 0 [[TicketQuery(status=closed,keywords~=firefox,count)]]
Number of closed Opera tickets: 0 [[TicketQuery(status=closed,keywords~=opera,count)]]
Number of closed tickets affecting Firefox and Opera: 0 [[TicketQuery(status=closed,keywords~=firefox opera,count)]]
Number of closed tickets affecting Firefox or Opera: 0 [[TicketQuery(status=closed,keywords~=firefox|opera,count)]]
Number of tickets that affect Firefox or are closed and affect Opera: 0 [[TicketQuery(status=closed,keywords~=opera,or,keywords~=firefox,count)]]
Number of closed Firefox tickets that don't affect Opera: 0 [[TicketQuery(status=closed,keywords~=firefox -opera,count)]]
Last 3 modified tickets: #376, #382, #381 [[TicketQuery(max=3,order=modified,desc=1,compact)]]

Details of ticket #1:

[[TicketQuery(id=1,col=id|owner|reporter,rows=summary,table)]]

Ticket Owner Reporter
#1 support@sherpa-mc.de anonymous
Summary first runs problems

Format: list

[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]

This is displayed as:

No results

[[TicketQuery(id=123)]]

This is displayed as:

#123
DecayOS throws NaNs with Amegic's integrator

Format: compact

[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]

This is displayed as:

No results

Format: count

[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]

This is displayed as:

0

Format: progress

[[TicketQuery(milestone=0.12.8&group=type,format=progress)]]

This is displayed as:

Format: table

You can choose the columns displayed in the table format (format=table) using col=<field>. You can specify multiple fields and the order they are displayed by placing pipes (|) between the columns:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]

This is displayed as:

Results (1 - 3 of 304)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#381 invalid MC@NLO cross section with Dire doesn't match fixed order Stefan Hoeche silvan
#377 fixed ee -> jjjj (RS) broken Enrico Bothmann Enrico Bothmann
#375 fixed ee -> jets MEPS@NLO example crashes Stefan Hoeche Enrico Bothmann
1 2 3 4 5 6 7 8 9 10 11

Full rows

In table format you can specify full rows using rows=<field>:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]

This is displayed as:

Results (1 - 3 of 304)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#381 invalid MC@NLO cross section with Dire doesn't match fixed order Stefan Hoeche silvan
Description

When generating events using the attached run card, the total cross section is off by a factor of 0.5 compared to fixed order. The cross sections reported during integrations are correct though.

#377 fixed ee -> jjjj (RS) broken Enrico Bothmann Enrico Bothmann
Description

Running Examples/Jets_at_LeptonColliders/LEP_Jets/Run.NLO.dat on rel-2-2-4 produces a giant cross section for ee -> jjjj (RS). Also the distributions are very awkward.

One can use the threshold_initialisation.patch for #375, as a workaround for the #375 crash.

The bug is quite old. If first occurs on trunk with r25928 ("check against kinematic and flavor mismatch in r jetcrit"), i.e. between the 2.1.1 and the 2.2.0 release. Note that the r25928 revision will only start integrating after applying r26025, which fixes a bug in the internal DY virtual ME.

Here are the integration results, note the 4.50949e+06 pb for the 2_4__e-__e+__j__j__j__j__QCD(RS) channel:

Read in channels from directory : Results/Amegic/MC_2_2__e-__e+__j__j__QCD(BVI)
Process_Group::CalculateTotalXSec(): Calculate xs for '2_2__e-__e+__j__j__QCD(BVI)' (Amegic)
2_2__e-__e+__j__j__QCD(BVI) : 31552.3 pb +- ( 232.279 pb = 0.736173 % )  exp. eff: 9.42397 %
Read in channels from directory : Results/Comix/MC_2_3__e-__e+__j__j__j__QCD(RS)
Process_Group::CalculateTotalXSec(): Calculate xs for '2_3__e-__e+__j__j__j__QCD(RS)' (Comix)
2_3__e-__e+__j__j__j__QCD(RS) : -373.379 pb +- ( 9.09491 pb = 2.43584 % )  exp. eff: 1.1781 %
  reduce max for 2_2__e-__e+__j__j__QCD(BVI) to 0.179983 ( eps = 0.001 )
  reduce max for 2_3__e-__e+__j__j__j__QCD(RS) to 0.515557 ( eps = 0.001 )
Read in channels from directory : Results/Amegic/MC_2_3__e-__e+__j__j__j__QCD(BVI)
Process_Group::CalculateTotalXSec(): Calculate xs for '2_3__e-__e+__j__j__j__QCD(BVI)' (Amegic)
2_3__e-__e+__j__j__j__QCD(BVI) : 11399.2 pb +- ( 518.311 pb = 4.54692 % )  exp. eff: 1.59119 %
Read in channels from directory : Results/Comix/MC_2_4__e-__e+__j__j__j__j__QCD(RS)
Process_Group::CalculateTotalXSec(): Calculate xs for '2_4__e-__e+__j__j__j__j__QCD(RS)' (Comix)
2_4__e-__e+__j__j__j__j__QCD(RS) : 4.50949e+06 pb +- ( 438975 pb = 9.73448 % )  exp. eff: 0.01594 %
  reduce max for 2_3__e-__e+__j__j__j__QCD(BVI) to 0.322027 ( eps = 0.001 )
  reduce max for 2_4__e-__e+__j__j__j__j__QCD(RS) to 0.894462 ( eps = 0.001 )
Read in channels from directory : Results/Comix/MC_2_4__e-__e+__j__j__j__j
Process_Group::CalculateTotalXSec(): Calculate xs for '2_4__e-__e+__j__j__j__j' (Comix)
2_4__e-__e+__j__j__j__j : 1704.02 pb +- ( 37.0925 pb = 2.17676 % )  exp. eff: 0.561434 %
  reduce max for 2_4__e-__e+__j__j__j__j to 0.618604 ( eps = 0.001 )
#375 fixed ee -> jets MEPS@NLO example crashes Stefan Hoeche Enrico Bothmann
Description

Running Examples/Jets_at_LeptonColliders/LEP_Jets/Run.NLO.dat crashes on the rel-2-2-4 branch. The only modification I did was to set the loop generator placeholders to

  LOOPGEN1:=BlackHat;
  LOOPGEN2:=BlackHat;
  LOOPMGEN:=OpenLoops;

However, the crash occurs when the BVI integration for ee -> jj starts, which should be taken of by the internal ME due to the default LOOPGEN0:=Internal; in the run card.

The binary search window might be quite large, because the same crash happens for rel-2-2-0 (sic!).

The crash happens in BBar_Emission_Generator::Active, because p_active is a null pointer at that time.

I've attached the print-out for the argument bviproc being passed to Active.

1 2 3 4 5 6 7 8 9 10 11


See also: TracQuery, TracTickets, TracReports

Last modified 14 months ago Last modified on Oct 8, 2018, 11:53:22 AM