A PHP Error was encountered

Severity: Warning

Message: Undefined array key "choices"

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated

Filename: models/Detail_model.php

Line Number: 71

Backtrace:

File: /var/www/html/application/models/Detail_model.php
Line: 71
Function: strpos

File: /var/www/html/application/controllers/Detail.php
Line: 252
Function: insertAPISummary

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated

Filename: helpers/my_audit_helper.php

Line Number: 8919

Backtrace:

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 8919
Function: str_replace

File: /var/www/html/application/controllers/Detail.php
Line: 255
Function: formatAIDetailSummary

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "choices"

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 257

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 257
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 257

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 257
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 258

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 258
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 258

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 258
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 259

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 259
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 259

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 259
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: file_get_contents(https://...@gmail.com&api_key=61f08fa0b96a73de8c900d749fcb997acc09): Failed to open stream: HTTP request failed! HTTP/1.1 429 Too Many Requests

Filename: helpers/my_audit_helper.php

Line Number: 143

Backtrace:

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 143
Function: file_get_contents

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 209
Function: simplexml_load_file_from_url

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 3098
Function: getPubMedXML

File: /var/www/html/application/controllers/Detail.php
Line: 574
Function: pubMedSearch_Global

File: /var/www/html/application/controllers/Detail.php
Line: 488
Function: pubMedGetRelatedKeyword

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Attempt to read property "Count" on bool

Filename: helpers/my_audit_helper.php

Line Number: 3100

Backtrace:

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 3100
Function: _error_handler

File: /var/www/html/application/controllers/Detail.php
Line: 574
Function: pubMedSearch_Global

File: /var/www/html/application/controllers/Detail.php
Line: 488
Function: pubMedGetRelatedKeyword

File: /var/www/html/index.php
Line: 316
Function: require_once

Automated Planning for Prostate Stereotactic Body Radiation Therapy on the 1.5 T MR-Linac. | LitMetric

AI Article Synopsis

Article Abstract

Purpose: Adaptive stereotactic body radiation therapy (SBRT) for prostate cancer (PC) by the 1.5 T MR-linac currently requires online planning by an expert user. A fully automated and user-independent solution to adaptive planning (mCycle) of PC-SBRT was compared with user's plans for the 1.5 T MR-linac.

Methods And Materials: Fifty adapted plans on daily magnetic resonance imaging scans for 10 patients with PC treated by 35 Gy (prescription dose [D]) in 5 fractions were reoptimized offline from scratch, both by an expert planner (manual) and by mCycle. Manual plans consisted of multicriterial optimization (MCO) of the fluence map plus manual tweaking in segmentation, whereas in mCycle plans, the objectives were sequentially optimized by MCO according to an a-priori assigned priority list. The main criteria for planning approval were a dose ≥95% of the D to at least 95% of the planning target volume (PTV), V (PTV) ≥ 95%, a dose less than the D to the hottest cubic centimeter (V ≤ 1 cm) of rectum, bladder, penile bulb, and urethral planning risk volume (ie, urethra plus 3 mm isotropically), and V ≤ 5%, V ≤ 10%, and V ≤ 35% to the rectum. Such dose-volume metrics, plus some efficiency and deliverability metrics, were used for the comparison of mCycle versus manual plans.

Results: mCycle plans improved target dose coverage, with V (PTV) passing on average (±1 SD) from 95.7% (±1.0%) for manual plans to 97.5% (±1.3%) for mCycle plans ( < .001), and rectal dose sparing, with significantly reduced V, V, and V ( ≤ .004). Although at an equivalent number of segments, mCycle plans consumed moderately more monitor units (+17%) and delivery time (+9%) ( < .001), whereas they were generally faster (-19%) in terms of optimization times ( < .019). No significant differences were found for the passing rates of locally normalized γ (3 mm, 3%) ( = .059) and γ (2 mm, 2%) ( = .432) deliverability metrics.

Conclusions: In the offline setting, mCycle proved to be a trustable solution for automated planning of PC-SBRT on the 1.5 T MR-linac. mCycle integration in the online workflow will free the user from the challenging online-optimization task.

Download full-text PDF

Source
http://www.ncbi.nlm.nih.gov/pmc/articles/PMC8850203PMC
http://dx.doi.org/10.1016/j.adro.2021.100865DOI Listing

Publication Analysis

Top Keywords

mcycle plans
16
mcycle
9
automated planning
8
stereotactic body
8
body radiation
8
radiation therapy
8
plans
8
manual plans
8
planning
6
dose
5

Similar Publications

Want AI Summaries of new PubMed Abstracts delivered to your In-box?

Enter search terms and have AI summaries delivered each week - change queries or unsubscribe any time!