Nova postagem

Encontrar

Pergunta
· Mar. 6, 2021

What is the difference between linear regression and logistic regression?

#Analytics #Machine Learning (ML) #Caché

When we have to predict the value of a categorical (or discrete) outcome we use logistic regression. I believe we use linear regression to also predict the value of an outcome given the input values.

Then, what is the difference between the two methodologies?

1 Comment
Discussão (1)0
Entre ou crie uma conta para continuar
Pergunta
· Mar. 3, 2021

How to update Ensemble - Business Hosts settings (default and custom settings) through code ?

#Implantação #Ambiente de Desenvolvimento #Ensemble

Hi ,

I have a requirement to programmatically fetch and update a Business Process Setting . It's a custom property , added in extended class .

I am trying find a sample, but no luck. 

Could any one help me ? 

3 Comments
Discussão (3)0
Entre ou crie uma conta para continuar
Discussão (1)0
Entre ou crie uma conta para continuar
InterSystems Oficial
· Fev. 11, 2021

Advisory: Incomplete Query Results with ‘ORDER BY <row ID field> DESC’ – HealthShare

#Alertas #Health Connect #HealthShare #InterSystems Oficial

February 11, 2021 – Advisory: Incomplete Query Results with ‘ORDER BY <row ID field> DESC’ – HealthShare

InterSystems has corrected a defect that can cause incomplete query results.  This defect affects the platforms underlying HealthShare and HealthShare Health Connect:

  • InterSystems IRIS and InterSystems IRIS for Health 2019.1.0, 2019.1.1, and 2020.1.0

See Alert: Incomplete Query Results with ‘ORDER BY <row ID field> DESC’ for further detail

Customers using HealthShare Personal Community should evaluate the number of proxy relationships they have established or removed. Customers that have established or removed proxy relationships more than 64,000 times are at risk for this defect.

Other than Personal Community, this defect does not affect query logic in the HealthShare or HealthShare Health Connect software.  However, Customers that have developed custom queries using the functions provided by InterSystems IRIS for Health, could be affected if they have the following HealthShare products and versions:

  • HealthShare 2019.2, 2020.1 and 2020.2
  • Health Connect 2019.1.0, 2019.1.1, 2020.1.0

A query can trigger the defect only if it meets all of the following conditions:

  • The query contains an ORDER BY clause sorting in descending (DESC) order.
  • The field used for that sorting is the table’s row ID.
  • The query contains conditions on multiple indexed fields.
  • The query selects data from only one table.

Users can modify an individual query to ensure correct results by replacing:

ORDER BY <row ID field> DESC

with

ORDER BY <row ID field>+0 DESC

The corrections for this defect are identified as DP-402745 and DP-403046 and will be included in all future product releases. They are also available via Ad hoc distribution from the InterSystems Worldwide Response Center (WRC).

This advisory is also on the InterSystems Product Alerts and Advisories page

If you have any questions regarding this advisory, please contact the Worldwide Response Center (WRC) at support@InterSystems.com or  +1.617.621.0700.

Discussão (0)0
Entre ou crie uma conta para continuar
InterSystems Oficial
· Fev. 11, 2021

Alert: Incomplete Query Results with ‘ORDER BY <row ID field> DESC’

#Alertas #Health Connect #InterSystems IRIS #InterSystems IRIS for Health #InterSystems Oficial

February 11, 2021 – Alert: Incomplete Query Results with ‘ORDER BY <row ID field> DESC’

InterSystems has corrected a defect that can cause incomplete query results. This defect affects:

  • InterSystems IRIS and InterSystems IRIS for Health 2019.1.0, 2019.1.1, 2019.2, 2019.3, 2019.4, 2020.1.0, 2020.2, and 2020.3
  • HealthShare Health Connect 2019.1.0, 2019.1.1, 2020.1.0
  • HealthShare Products 2019.2, 2020.1 and 2020.2

(In HealthShare and HealthShare Health Connect, this defect only affects Personal Community with 64,000 patient proxies and possibly customer-built custom queries. For more details on how this defect affects HealthShare, please see Advisory: Incomplete Query Results with ‘ORDER BY <row ID field> DESC’-HealthShare)

A query can trigger the defect only if it meets all of the following conditions:

  • The query contains an ORDER BY clause sorting in descending (DESC) order
  • The field used for that sorting is the table’s row ID
  • The query contains conditions on multiple indexed fields
  • The query selects data from only one table

You can modify an individual query to ensure correct results by replacing

ORDER BY <row ID field> DESC

with

ORDER BY <row ID field>+0 DESC

Note that some InterSystems search utilities, including the Interoperability Message Viewer, use queries that could be affected by this defect and cannot be edited. The only way to mitigate this defect system-wide is to install a version that includes the corrections.

The corrections for this defect are identified as DP-402745 and DP-403046 and will be included in all future product releases. They are also available via Ad hoc distribution from the InterSystems Worldwide Response Center (WRC).

If you have any questions regarding this alert, please contact the Worldwide Response Center.

Discussão (0)0
Entre ou crie uma conta para continuar