| Version 4 (modified by , 3 years ago) ( diff ) |
|---|
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: | 6 | [[TicketQuery(status=new&milestone=,count)]]
|
| Number of new tickets: | 6 | [[TicketQuery(status=new,count)]]
|
| Number of reopened tickets: | 1 | [[TicketQuery(status=reopened,count)]]
|
| Number of assigned tickets: | 1 | [[TicketQuery(status=assigned,count)]]
|
| Number of invalid tickets: | 13 | [[TicketQuery(status=closed,resolution=invalid,count)]]
|
| Number of worksforme tickets: | 13 | [[TicketQuery(status=closed,resolution=worksforme,count)]]
|
| Number of duplicate tickets: | 1 | [[TicketQuery(status=closed,resolution=duplicate,count)]]
|
| Number of wontfix tickets: | 7 | [[TicketQuery(status=closed,resolution=wontfix,count)]]
|
| Number of fixed tickets: | 107 | [[TicketQuery(status=closed,resolution=fixed,count)]]
|
| Number of untriaged tickets (milestone unset): | 8 | [[TicketQuery(status!=closed,milestone=,count)]]
|
| Total number of tickets: | 149 | [[TicketQuery(count)]]
|
| Number of tickets reported or owned by current user: | 9 | [[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
|
| Number of tickets created this month: | 3 | [[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: | #220, #195, #205 | [[TicketQuery(max=3,order=modified,desc=1,compact)]]
|
Details of ticket #1: |
| |
| ||
Format: list
[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
This is displayed as:
No results
[[TicketQuery(id=123)]]
This is displayed as:
- #123
- BKG caster does not actively close server connections
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:
Format: progress
[[TicketQuery(milestone=0.12.8&group=type,format=progress)]]
This is displayed as:
defect
103 / 107
enhancement
24 / 27
task
14 / 15
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 in 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 141)
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 141)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #221 | fixed | RTCM3 MSM QZSS L1C/B support | ||
| Description |
Have noticed Trimble Alloy and Septentrio PolaRx5 RTCM3 MSM streams now including a new signal that appears to be 1E. Septentrio note in their 5.7.0 firmware update that the QZSS L1C/B signal can now be enabled in RTCM3 MSM streams. This mapping has been added to the RTKLIB fork see https://github.com/rtklibexplorer/RTKLIB/blob/main/src/rtcm3.c#L106 Made a similar addition to a local BNC build and it appears to be logging the RTCM streams to rinex files as expected - it did need local skeleton files that added the 1E signal. Noted some header defaults in src/rinex/rnxobsfile.cpp and signal priorities, and should QZSS 1E be added to these, it does not seem necessary for logging as stream to rinex. Index: src/RTCM3/RTCM3Decoder.cpp
===================================================================
--- src/RTCM3/RTCM3Decoder.cpp (revision 10930)
+++ src/RTCM3/RTCM3Decoder.cpp (working copy)
@@ -356,12 +356,12 @@
static struct CodeData qzss[RTCM3_MSM_NUMSIG] = {
{0.0, 0},
{GPS_WAVELENGTH_L1, "1C"},
+ {GPS_WAVELENGTH_L1, "1E"},
{0.0, 0},
{0.0, 0},
{0.0, 0},
{0.0, 0},
{0.0, 0},
- {0.0, 0},
{QZSS_WAVELENGTH_L6, "6S"},
{QZSS_WAVELENGTH_L6, "6L"},
{QZSS_WAVELENGTH_L6, "6X"},
|
|||
| #220 | fixed | Question about code BIA states and ionosphere constraints in BNC PPP | ||
| Description |
Dear BNC developers, I am currently studying the PPP/PPP-AR model implemented in BNC 2.13.6, especially the dual-frequency uncombined PPP parameterization in the src/PPP/ path. I would like to ask for clarification about the theoretical interpretation of the code BIA states and the ionosphere constraint model in BNC. In a GPS-only test configuration, for example: PPP/lcGPS=P12&L12 PPP/constraints=no my understanding is that the LC string is parsed as: cG1, cG2, lG1, lG2 At the same time, the PPP filter creates the following code-bias-like states: BIA cG1 BIA cG2 together with per-satellite ionosphere states ION and per-satellite, per-phase-LC ambiguity states. From my current reading of the source code and the PPP output, BIA cG1/cG2 appear to be real Kalman filter states, not merely diagnostic output quantities. We also noticed that the common mode of BIA cG1/cG2 is datum-coupled with the receiver clock. BNC seems to regularize this direction through the prior variance of the code BIA states, for example through aprSigCodeBias. Therefore, we do not think that the absolute values of BIA cG1/cG2 should be interpreted as independently observable physical receiver code hardware delays. According to my understanding of conventional dual-frequency UDUC PPP, when no external ionosphere product is used as a constraint, receiver code biases are usually not estimated as a separate receiver DCB parameter. Instead, they are absorbed through re-parameterization into receiver clock, ionosphere states, ambiguities, and related datum definitions. Explicit handling of receiver DCB becomes necessary mainly in ionosphere-constrained PPP, where GIM, SSR/VTEC/STEC, or regional ionosphere products are used to constrain the ionosphere states. Otherwise, receiver code biases may contaminate the ionosphere states and cause datum inconsistency with the external ionosphere constraints. Therefore, my main question is why BNC still estimates BIA cG1/cG2 for the dual-frequency code LCs even when: PPP/constraints=no This seems different from a conventional minimal full-rank UDUC PPP parameterization. It looks more like a code-LC-wise bias-like nuisance-state parameterization. Under this interpretation, BIA cG1/cG2 can be re-parameterized into a receiver-clock common component and a receiver-DCB-like differential combination, for example: DCB_like = BIA cG2 - BIA cG1 However, the absolute values of BIA cG1/cG2 would then be datum-dependent and prior-dependent. Could you please help clarify the following points?
I am asking these questions because this implementation appears to differ from some common IC-PPP formulations in the literature, where receiver DCB is explicitly handled mainly when external ionosphere constraints are introduced. In BNC, the BIA cG* states look more like code-LC-wise bias-like nuisance states, and they seem to be used independently of whether ionosphere constraints are enabled. I would like to understand and document the BNC model correctly and avoid misinterpreting these states as directly observable physical receiver hardware delays. Thank you very much for providing BNC as open-source software, and thank you in advance for your help in clarifying these model details. Best regards, Melissa Grove |
|||
| #219 | worksforme | make me download this pls | ||
| Description |
Hello, i'd like to download the ntrip files but it seems like you can only download them one at a time, i'm a uni student doing a project. |
|||
See also: TracQuery, TracTickets, TracReports
