the f_lstm_score and b_lstm_score is always zero?

[demonking2]

so i ran the script of yours but during every epoch i am getting forward lstm score and backward lstm score as zero.Could you please care to explain?

[rudy-letote]

I ran the "predict_compability.sh".the compability score of "1" lable and "0" label is almost the same .they are all in (-8 ,-10), in my opinion ,i think the compability score of "1" lable should differ from the "0" lable.can you explain it or where is my falut。the bellow are 20 scores of lable "1" and lable "0" respectively:
is compability:[-7.720056, -8.97509, -8.220935, -10.582401, -7.236626, -8.232678, -8.558042, -9.792898, -10.399817, -10.043319, -9.066071, -10.162157, -7.694268, -7.881978, -9.96062, -7.8345957, -7.8045917, -11.626244, -8.886615, -6.884479, -6.2776566, -9.196812, -7.628573, -10.240056, -7.336111, -7.787043, -8.410638, -9.365236, -10.182903, -10.997128, -8.968154, -9.943468, -7.5123353, -6.9027557, -10.395691, -7.4805303, -7.5589123, -10.828439, -8.110326, -6.815978]
not compability [-8.955776, -8.421998, -9.673913, -8.750407, -10.038454, -9.748418, -8.768893, -9.60205, -12.77886, -9.944672, -11.759442, -9.369885, -8.797088, -8.776102, -8.981208, -8.810187, -9.318503, -9.157499, -12.087228, -11.080102, -8.174597, -7.7694826, -9.0620365, -8.552005, -9.9986105, -8.610872, -8.793626, -9.544354, -13.876475, -9.736692, -10.6651, -8.750646, -8.793308, -8.21271, -7.4728117, -8.3004465, -9.868675, -8.257614, -11.120394, -10.088629]

[xthan]

I do not know the reason. What is the AUC you are getting?

[rudy-letote]

0.905623 for 7076 outfits

…

--------------原始邮件-------------- 发件人："Xintong Han "<notifications@github.com>; 发送时间：2018年10月22日(星期一) 晚上8:10 收件人："xthan/polyvore" <polyvore@noreply.github.com>; 抄送："rudy-letote "<rudy.li@letote.cn>;"Comment "<comment@noreply.github.com>; 主题：Re: [xthan/polyvore] the f_lstm_score and b_lstm_score is alwayszero? (#11) ----------------------------------- I do not know the reason. What is the AUC you are getting? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.