Skip to content

Log file print line at start #187

@JohnHadish

Description

@JohnHadish

The similarity step can take awhile depending on how large the file is. The first line the similarity step prints to the log file is when it completes 1% of the similarity correlations. This means that you will have an empty log file untill it prints the first percentage:

# cat log.log
 0: 1%	3m12s	5h16m48s
 0: 2%	5m27s	4h27m3s
 0: 3%	7m16s	3h54m57s

Request: Have KINC print a line to the log file as soon as it starts. This will show the user that the program is actually running. It is nerve racking to have a log file which has been running for 10 minutes that does not have any output in it.
Suggestion Have KINC print which files it is going to use for the step it is currently on.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions