rpytel1 log-strategy issues

rpytel1 / log-strategy

Project conducted for Seminar in Machine Learning for Software Engineering. Aim of our research was to explore possible directions of Deep Learning solutions for log detection in a snippet of code.

0 stars 1 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Feature/readme

#23 jan-gerling closed 4 years ago
0
Feature/test data02

#22 jan-gerling opened 4 years ago
0
Feature/evaluation

#21 jan-gerling closed 4 years ago
0
Feature/test data

#20 jan-gerling closed 4 years ago
0
Feature/scenarios

#19 rpytel1 closed 4 years ago
0
Refactor/code2vec

#18 jan-gerling closed 4 years ago
0
Refactor

#17 jan-gerling closed 4 years ago
0
Feature/training data

#16 jan-gerling closed 4 years ago
0
Scenarios to train and test results

#15 rpytel1 opened 4 years ago
0
Classifier

#14 jan-gerling opened 4 years ago
2
Labeled code vectors pre trained code2vec (not issue but link share)

#13 CasperSchroder opened 4 years ago
7
The output of organizeData.py doesnt include the function definition/signature/declaration wtv u want to call it

#12 Dekelv closed 4 years ago
1
DO NOT REMOVE LOG LINES, instead change them to "/* */" because it affects code2vec's vectors

#11 CasperSchroder opened 4 years ago
0
Feature/parser

#10 jan-gerling closed 4 years ago
0
Loading pretrained model

#9 rpytel1 opened 4 years ago
1
Logger extractor

#8 rpytel1 closed 4 years ago
0
Pipeline scheme

#7 rpytel1 opened 4 years ago
0
Components

#6 jan-gerling closed 4 years ago
0
Training components

#5 rpytel1 closed 4 years ago
4
Datasets used by papers proposed by course

#4 CasperSchroder closed 4 years ago
0
Probably useful papers

#3 CasperSchroder opened 4 years ago
1
Keep the Date

#2 jan-gerling opened 4 years ago
0
Reader

#1 jan-gerling opened 4 years ago
0