Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18390
If the label-specific metrics are already exposed in the multiclass metrics
output, why do we need this too?
---
-
To unsubscribe
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user thesuperzapper commented on the issue:
https://github.com/apache/spark/pull/18390
@MLnick @WeichenXu123 sorry to ping again, but what is currently stopping
this from merging?
---
-
To unsubscribe, e-mail
Github user thesuperzapper commented on the issue:
https://github.com/apache/spark/pull/18390
@MLnick @WeichenXu123 whether or not we implement this PR, we still need to
expose precision/recall in MulticlassClassificationEvaluator, rather than the
mostly useless weightedPrecision/weig
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user rawataaryan9 commented on the issue:
https://github.com/apache/spark/pull/18390
@MLnick Can you please have a look at the changes as per the discussion
above and comment regarding the build failure issue.
---
If your project is set up for it, you can reply to this email
Github user rawataaryan9 commented on the issue:
https://github.com/apache/spark/pull/18390
@MLnick Can you please have a look and guide me towards the issue with the
build failure.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18390
**[Test build #78799 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78799/testReport)**
for PR 18390 at commit
[`dd1fb3f`](https://github.com/apache/spark/commit/d
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78799/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18390
**[Test build #78799 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78799/testReport)**
for PR 18390 at commit
[`dd1fb3f`](https://github.com/apache/spark/commit/dd
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78792/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18390
**[Test build #78792 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78792/testReport)**
for PR 18390 at commit
[`4f91ba3`](https://github.com/apache/spark/commit/4
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18390
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18390
**[Test build #78792 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78792/testReport)**
for PR 18390 at commit
[`4f91ba3`](https://github.com/apache/spark/commit/4f
Github user rawataaryan9 commented on the issue:
https://github.com/apache/spark/pull/18390
@MLnick I have incorporated all the suggested changes. Kindly have a look.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If you
28 matches
Mail list logo