Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Alexei B.

Pages: 1 [2] 3 4 ... 6
Versions - Release History / PDC core versions 1030-1041
« on: November 22, 2017, 01:17:51 PM »
- Changed the initial source extraction algorithm. The new algorithm ensures possible sources are found, as the old one has siezed to function.
- Due to the framework changed, new versions give a different computer ID. This meanslicenses are to be re-initialized, if updating from an old version.

- Multiple fixes in localizations.
- Multiple fixes regading compatibility with both old and new version of Windows.
- Updated compatibility with secure resources to prevent failing of resources using new versions of TLS.
- Other changes.

Again Norton detects latest version as "WS.Reputation.1".
Submitted false-positive report to them. should be working fine in a few days.

FAQ - Frequently Asked Questions / Re: Licence
« on: October 17, 2016, 03:14:35 PM »
Plagiarism Detector licenses are not limited in time.
You may always contact our support service for a license re-initialization (new OS/PC, etc.)

PDAS licenses are monthly subscriptions for individual clients.


Please, be more exact about your problem.

"Plagiarism Detector" general discussion / Re: self sitation
« on: August 31, 2016, 12:52:55 PM »

Please pay attention to the message above. It explains how to use the Internet-references feature.

"Plagiarism Detector" - Bugs\Errors\Crashes / Re: Problem
« on: June 11, 2016, 01:10:53 AM »
In this case, please contact our support via e-mail. Please don't forget to mention your license code.

Feel free to ask any additional questions.

Versions - Release History / PDC core versions 914-915
« on: March 25, 2016, 03:29:00 PM »
- Important: Fixed a problem, when clustering distance was the same for both presets (Arts&Sciences). Results from this version and on will be different from previous versions ad are to be more exact. Any feedback is appreciated.

- New long-awaited feature added for testing purposes: saving reports to PDF ! It will be in testing for some time and we hope it will be then added on a regular basis. Reports are uploaded to our servers for conversion and you then download the result.

Versions - Release History / PDC core versions 911-912
« on: March 22, 2016, 11:22:13 PM »
Mostly ARV changes:
- Added button to save the list of reports to CSV
- Added button to save the report to HTML file to a desired location
- Re-worked reports so that a notification is seen, when an incorrectly re-saved report is opened.
- Slightly changed coloring for reports with lots of failed resources (planning to divide fails due to a client computer from those generated by servers)
- New graph in reports, mouseover highlights top source for a selected section.
- Added a new panel below and changed elements distribution. More elements to come.

"Silver Bullets" / Re: Resources Error Codes
« on: March 18, 2016, 03:55:42 PM »
New information added to the report for failed resources:
1. Browser error message now displayed.
Resource Download Failed. Means that the resource was not downloaded and thus was not analyzed.

Get Response Failed. Means the resource was not downloaded because the site had not provided the response to the request.

"Plagiarism Detector" - Bugs\Errors\Crashes / Re: Problem with V895
« on: December 02, 2015, 04:53:57 AM »
Another recommendation would be to unlock the ability for a customer to use the previous version of the software

This would have been done, if it were possible. It was not our wish to force updating to the latest version, but the need. Due to some third party changes, versions 850 and bellow started providing totally inadequate results (very poor detection), thus we were to force-update our clients.

T-comparator presets are not so easily changed. Presets currently used are based on the algorithms developed for PAN'14 conference, plagiarism detection task, and showed one of the best results with the used document corpus. One of the lines of our research now is what is different between that corpus and the "real-life" cases, which can be closely connected to the problem you report.

Changing the preset in the current system requires some research, as we need to be sure the new preset works better. At present we have started additional tests on the false-positive detection and upon the results we will both post here and may start making the needed alterations.

"Plagiarism Detector" - Bugs\Errors\Crashes / Re: Problem with V895
« on: November 21, 2015, 11:25:49 PM »
Like you were informed, we will consider the detection threshold for the Arts. However as of now we don't see enough reason to change it - this preset is aimed at detecting obfuscated plagiarism and our tests showed it deals with this problem just fine.

We need enough evidence of false-positives with this preset to change it. We are ready to analyze each such case and we have some of them stored already. But the number of such cases is not yet enough to start such changes.

We recommend to use word-to-word preset when it is necessary to avoid false-positives.

"Plagiarism Detector" general discussion / Re: license Difference
« on: November 04, 2015, 01:03:36 PM »
Thank you for your interest in our software!

Lite is the most basic license. We are now reviewing differences between Lite and Personal licenses, so these will be different in the next version.

Pro - this license gives access to all features, and besides provides licenses for two computers.

Portable - this gives additional license to be used from your USB/Flash drive.

All the prices are available from our site:

Feel free to ask any additional questions.

Versions - Release History / PDC core versions 888-889 - major update
« on: September 24, 2015, 03:43:16 PM »
Plagiarism Detector major update with core version 888:


01. Added check type selection window to the Step-by-Step Wizard. More details here:,337.
02. Added failed resources notification. More details here:,48.0.html
03. New T-comparator is now used for comparing documents. It is more precise, yet creates more load on CPU and memory. Due to this change, results from previous versions can differ from current results.
04. Changed license information text on the mains screen to avoid misunderstanding

1. Fixed an issue, resulting from third-party changes, that made previous versions returning "no plagiarism" results for most document. Force-updating from previous versions due to this fix.

We are highly looking towards your feedback!

"Silver Bullets" / Re: Check Type: Word-to-Word VS Re-Written
« on: September 18, 2015, 05:03:31 PM »
The Exact Sciences.

Text in these fields of knowledge showed certain features of their own, making the above-mentioned obfuscated Plagiarism detection algorithms unacceptable on many cases. Texts in Physics, Maths, etc. usually are much less flexible and enjoy a massive use of domain-specific constructions and expressions that are similar to many texts from the same domain of knowledge. One of the best examples was a certain medical prescription, which was considered Plagiarized upon checking. However a manual check did not confirm it. It turned out that most (if not all) of prescriptions use the same structure of the text as well as the same words and expressions. It is just the components, that change.

Let us take this example from Wikipedia:
“Take of pentobarbitone sodium, three grammes
of sulphate of morphia, two grammes
of hydrate of chloral, fifteen grammes
of table sugar, enough to make fifty grammes.”
And now let’s toss the ingredients randomly:
“Take of hydrate of chloral, three grammes
of pentobarbitone sodium, two grammes
of sulphate of morphia, fifty grammes
of table sugar, enough to make fifteen grammes.”

And now remember the example from the Arts section that was to be detected as Plagiarism. It is rather evident, that due to the same language used these parts will be considered the “same” text, that was obfuscated by changing the word order (one of the approached to obfuscation).

Sure, it is an error, one that we call false-positive. Errors of this kind are usual for all the Plagiarism detection algorithms that are aimed at detecting obfuscated Plagiarism.

Having it in mind, we modified the algorithm specifically for such texts, to detect only what we call “word-to-word” Plagiarism. This algorithm will correctly detect this “prescription” as two different texts, but will also detect those “Arts” example as different texts.

So this “word-to-word” Plagiarism Detection algorithm has the following features:
-   Detects only similar parts of texts
-   Prevents false-positive results
-   Usually shows less Plagiarism then a regular algorithm
-   Is bad at finding even slightly obfuscated Plagiarism

In the recent years we have had several versions of Plagiarism Detector, using this algorithm, and they were provided to customers, that required this kind of check. However having two very different versions is not what we see right, so our RnD spent much time on incorporating both algorithms into a single software!

"Silver Bullets" / Re: Check Type: Word-to-Word VS Re-Written
« on: September 18, 2015, 05:02:28 PM »
The Arts.

Texts in these subjects are very flexible in nature and allow much modification without actually changing the meaning. Any analysis of a piece of literature is a good example to it. To detect Plagiarism in the best possible way a software has to detect obfuscated “re-written” cases of Plagiarism – when sentences are modified (manually or automatically) to keep the meaning, but avoid detection. We have multiple cases of such modified documents, provided by our customers at different times, which shows some students’ struggle to avoid Plagiarism detection. For example the sentence “It was a need for him to have the computer fixed” is better be detected as similar to “he must have had the PC fixed”. Please note: these examples are hypothetical and very simplified, the algorithm is much more complex and this pair can be detected or not, depending on the context.

Such approach to Plagiarism detection is perceived to be better not only by us, but also by many competitors, and that is due to several advantages:
-   Obfuscated Plagiarism detection
-   More Plagiarism detected – users often compare software by the detection percent for the same document

That is why it has usually been a default setting for our software.
However, this approach was found to have a significant drawback:
-   False-positive results for certain documents (see below)

Pages: 1 [2] 3 4 ... 6