Bugs Weka 3.8.6 - weka

After loading a dataset diabetes.arff and then choosing a classifier such as J48, I can start one test and after that the button "start" becomes disabled. Even clicking on stop it continues disabled. I changed the classifier to ZeroR and then the button became enabled again, but it does not work.I clicked several times and nothing. I also reinstalled Weka and tried other datasets, but every time the same problem.
I recorded a video to show this bug on https://1drv.ms/v/s!ApZk5TJm2dA3odp28KVQSssv34Lu4Q?e=uyrTD7

As an alternative, you could try the Weka Investigator, a more powerful tool than the Weka Explorer. The Investigator is part of the ADAMS framework. For your purposes, you can download the adams-ml-app snapshot from the snapshot download page
Have a look at the video of my talk from the Weka User Conference 2021, for an introduction to the tool.

Related

Why does the VS Solution Explorer Script Documents list keep growing and how do I use those links?

When we debug an MVC5 application, links are provided to access the running scripts as shown below. This is for a basic MVC5 application that has had absolutely no modifications:
If we simply refresh the screen 3 times on the home page, the list displayed gets longer as shown below:
I've never really tried to debug a script yet. I have used the html links to view pages and I understand I can open one of the .js files, set a breakpoint and try to debug a script. But why are there so many links?. I would have thought I only need a single link for any given script or page that is in progress; that the links would go away when the script or page is no longer active. Clearly I'm missing something about the constantly growing list.
Could someone provide a brief explanation of this feature and how I will use it. My book on Visual Studio mentions this feature, but doesn't provide enough text for me to get a handle on this aspect of the feature.
This looks like a bug in the Edge debug adapter. Specifically, the adapter is supposed to send an event when the page refreshes (or a navigation occurs) to clear out old scripts that are no longer valid for the new execution context (here's a link to the event description in the debug adapter protocol if you're curious).
We've opened an issue on the GitHub project where you can track the progress of the fix.
For a workaround in the mean time, if you click on the bottom-most duplicate script in the list, that should be the latest loaded version, and should work without error.
*EDIT:
We've got a fix for the issue which should be out with 16.2 Preview 2 of Visual Studio.

Historical or Extended test history

Will allure provide a historical report of all the tests that have been run over a long period of time? I am open to other options as well. I am looking for a solution to having a bunch of individual test reports. Previously, Extent Reports has been used but would rather to have all the results in a centralized area that is available to all.
Update: we use Selenium, junit, cucumber, and java
Take a look at Klov.
Docs
Demo
There you have a "Builds" menu where you can see all the reports.
I like it because:
The testcases are updated in real time after execution
I can track progress on different versions
What I don't like:
Screenshots issue
Description and Author are not displayed
Hope it helps!

XPages are rebuilt automatically when opening designer

I have a customer who likes to do some basic stuff in Domino Designer in a specific database. He only works with Forms, agents etc and never do any Xpages stuff. I have done all the xpages stuff in the Database.
This morning when I opened designer I can see that almost all of the xpages design object has been signed by him. but he has not opened any of the xpages design objects. (only forms) and have not signed the application.
When I look at the webpage I can see that the designn changes I did from a few days back have disapeared, so I seem to be looking at an older version of my webpage.
If I go in to the application and Build the application with my id everything is back to normal.
This scenario seem to repeat only a few times a week even though my customer do changes to the application every day.
Image show the xpages time stamp this morning which seem to be about the same time my customer opened the application in designer.
Currently we are both using 9.0.1 FP10 but I have also seen this problem before FP10
ps.
Not sure if it is related but my customer also have another version of Domino Designer (8.5.3 Swedish) which he use when signing agents as signing them with v9 cause them to not work.
What can be the cause of this behaviour and how can I avoid it.
thanks
Thomas
Open Designer. From the top menu, select Project > Build Automatically and ensure it is disabled (not checked).
For additional reading, refer to Nathan T. Freeman's wonderful article "Taming Domino Designer" https://nathantfreeman.files.wordpress.com/2013/04/tamingdesigner.pdf
I am pretty sure that it's the 8.5.3 Designer that does the rebuild when opening the database in Designer. So this happens when the user just wants to sign some agents.
This problematic behaviour has been fixed in 9.0.1 (or perhaps in a fix pack release of 9.0.1). See this IBM technote about the problem: http://www-01.ibm.com/support/docview.wss?uid=swg1LO80591

Sitecore 8.1 Multivariate testing optimization shows no test status

I have set up a Multivariate test in Sitecore 8.1. In Experience Editor i have a notification,it says item has a active test and Optimization tab shows red button but status shows no tests. I did check in the analytic database no test record found. I did deploy the Test from Workflow and its running. I am getting all options to stop, cancel and suspend. Sitecore is not testing my variations can any one help me to resolve this?
From what you are describing it sounds like the Sitecore_testing_index is erroneous. Perhaps the index is invalid, not built or not present. This index is required for Sitecore's Experience Optimisation to find the Tests in their various states.
I recommend getting a default copy of Sitecore.ContentTesting.Solr.IndexConfiguration.config from a fresh install and copy it to the path App_Config/Include/ContentTesting.
Once that is done, rebuild the Index via the Index Manager. You should then be able to find tests in the Experience Optimisation.
If you're still having trouble I recommend replacing the entire contents of App_Config/Include/ContentTesting with the files from a fresh install. And re-indexing.
I also recommend having a look against the Item which has the Multivariate test it should be within the default field Page Level Test Set. It should have values something along the lines of this
If it is populated but you are still unable to the Test, follow this guide how to create Multivariate Tests in Sitecore to identify where something is going wrong.

How to get consolidated report of project mile stones for all projects in Redmine

We are Redmine as a Project management tool. It has been working great and we are happy with it. We now have a new requirement now. Our management wants to see a report showing each project's delivery date, manager, start date, total issues, open issues, closed issues. I searched at several places for quite some time and did not get a solution. I appreciate if someone can offer help.
This is, for me personally, the single thing JIRA is better at :)
Anyway, that being said, you can get a summary of all open versions on your "my page", eh, page, by using this plugin:
https://github.com/bradbeattie/redmine-my-widgets-plugin
And you can also add custom queries to "my page".
You can get much of what you want in the issue report. Click the Summary button in the sidebar of the issues page in each project. Example
Create one generic top level project. Calendar, gantt charts, issues, etc, for the top level project will show everything for every project that's nested underneath.
If you are properly adding roadmaps/milestones to all the projects, you can use My Roadmaps plugin to get a consolidated visibility:
http://www.redmine.org/plugins/my_roadmaps
It works fine with 1.2 and 1.4 versions.