Some Suggestions and one bug (?)

[dsdoermann]

I want to again express my thanks for this tool. I can see it evolving and it is great.

Previously I had some scripts that processed the tex file before passing it to detex. I don't know how your code works, but here are a few things I found useful for avoiding Grammarly errors when there were none.

1) For cite and refs, before detex I prepend a token "CITE" (CITE\cite{}), then when the latex is removed, the text still shows "in CITE" and no Grammarly error is generated.

2) I remove all double spaces since they don't matter in latex. (Again I don't know how your code works)

3) Im getting a situation when I have a comma after a \cite, showing up a period in the text. "Multi-PIE dataset \cite{multipie}, which" shows up as " Multi-PIE dataset. which " in the text panel, which generates a Grammarly error

4) It seems there is a problem with the text area if there are two citations in one line?

The loss function used is the same as in \cite{DBLP:journals/corr/abs-1710-00925}. The loss function has two components, the bin classification component and the regression component. Bin classification uses stable softmax and cross-entropy, which helps the network predict the pose's neighborhood. N. Ruiz et al. \cite{DBLP:journals/corr/abs-1710-00925} calculated three entropy losses, one for each angle, and backpropagated it through the network to improve learning. They computed the expectation of each output angle from the binned output to obtain the fine-grained prediction. The regression loss was calculated using the Mean Square Error loss to improve the fine-grained prediction. The alpha value is a hyperparameter used for the regression loss function, and the weight of the classification loss is constant.

shows up in textarea as

The loss function used is the same as in calculated three entropy losses, one for each angle, and backpropagated it through the network to improve learning. They computed the expectation of each output angle from the binned output to obtain the fine-grained prediction. The regression loss was calculated using the Mean Square Error loss to improve the fine-grained prediction. The alpha value is a hyperparameter used for the regression loss function, and the weight of the classification loss is constant.

So everything is missing between the two citations.

[robindijkhof]

Thanks, I'll check it out. Your first point can be achieved by using custom filters. Something like this would work:

filter: /(\cite{)(.*?)(})/g value: CITE

[dsdoermann]

Thank you so much! I just realized that there are custom filters. I'll try that next time. I'm not a great programmer anymore, but I think I can handle some regex!

I also see a sync scroll now, but I don't remember updating. Do I need to update to get the latest version manually? May it be nice to have the version or version date on the plugin on the toolbar?

Dave

---

David Doermann Professor, SUNY Empire Innovation Professor, Department of Computer Science and Engineering University at Buffalo

email: @.*** website: cse.buffalo.edu/~doermannhttp://cse.buffalo.edu/~doermann phone: 716-645-1557 (office), 410-493-9043 (mobile)

[footer_logo_03]

From: robindijkhof @.> Sent: Monday, July 19, 2021 6:03 AM To: robindijkhof/overleaf-textarea @.> Cc: David Doermann @.>; Author @.> Subject: Re: [robindijkhof/overleaf-textarea] Some Suggestions and one bug (?) (#50)

Thanks, I'll check it out. Your first point can be achieved by using custom filters. Something like this would work:

filter: /(\cite{)(.*?)(})/g value: CITE

- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frobindijkhof%2Foverleaf-textarea%2Fissues%2F50%23issuecomment-882418343&data=04%7C01%7Cdoermann%40buffalo.edu%7Cbc383af2d1e44224a1d708d94a9c6521%7C96464a8af8ed40b199e25f6b50a20250%7C0%7C0%7C637622857842435091%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=neToqnx5fZoTT%2Ba%2BE00A1B0iisp3Of%2BQcfAVXQVizCA%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKONP73ZHJGHHMYTGDIZQVDTYPZ5LANCNFSM5APUP3OQ&data=04%7C01%7Cdoermann%40buffalo.edu%7Cbc383af2d1e44224a1d708d94a9c6521%7C96464a8af8ed40b199e25f6b50a20250%7C0%7C0%7C637622857842435091%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=bYtwsuipJi7KnHxPt82ftcY%2Fq1qN8Q3U49GaizDiYxg%3D&reserved=0.

[dsdoermann]

Just FYI, I needed double slash to get it to work.

Thanks!

---

David Doermann Professor, SUNY Empire Innovation Professor, Department of Computer Science and Engineering University at Buffalo

email: @.*** website: cse.buffalo.edu/~doermannhttp://cse.buffalo.edu/~doermann phone: 716-645-1557 (office), 410-493-9043 (mobile)

[footer_logo_03]

From: robindijkhof @.> Sent: Monday, July 19, 2021 6:03 AM To: robindijkhof/overleaf-textarea @.> Cc: David Doermann @.>; Author @.> Subject: Re: [robindijkhof/overleaf-textarea] Some Suggestions and one bug (?) (#50)

Thanks, I'll check it out. Your first point can be achieved by using custom filters. Something like this would work:

filter: /(\cite{)(.*?)(})/g value: CITE

- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frobindijkhof%2Foverleaf-textarea%2Fissues%2F50%23issuecomment-882418343&data=04%7C01%7Cdoermann%40buffalo.edu%7Cbc383af2d1e44224a1d708d94a9c6521%7C96464a8af8ed40b199e25f6b50a20250%7C0%7C0%7C637622857842435091%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=neToqnx5fZoTT%2Ba%2BE00A1B0iisp3Of%2BQcfAVXQVizCA%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKONP73ZHJGHHMYTGDIZQVDTYPZ5LANCNFSM5APUP3OQ&data=04%7C01%7Cdoermann%40buffalo.edu%7Cbc383af2d1e44224a1d708d94a9c6521%7C96464a8af8ed40b199e25f6b50a20250%7C0%7C0%7C637622857842435091%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=bYtwsuipJi7KnHxPt82ftcY%2Fq1qN8Q3U49GaizDiYxg%3D&reserved=0.

[dsdoermann]

And somehow that fixes the "bug" I suggested.

---

David Doermann Professor, SUNY Empire Innovation Professor, Department of Computer Science and Engineering University at Buffalo

email: @.*** website: cse.buffalo.edu/~doermannhttp://cse.buffalo.edu/~doermann phone: 716-645-1557 (office), 410-493-9043 (mobile)

[footer_logo_03]

From: robindijkhof @.> Sent: Monday, July 19, 2021 6:03 AM To: robindijkhof/overleaf-textarea @.> Cc: David Doermann @.>; Author @.> Subject: Re: [robindijkhof/overleaf-textarea] Some Suggestions and one bug (?) (#50)

Thanks, I'll check it out. Your first point can be achieved by using custom filters. Something like this would work:

filter: /(\cite{)(.*?)(})/g value: CITE

- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frobindijkhof%2Foverleaf-textarea%2Fissues%2F50%23issuecomment-882418343&data=04%7C01%7Cdoermann%40buffalo.edu%7Cbc383af2d1e44224a1d708d94a9c6521%7C96464a8af8ed40b199e25f6b50a20250%7C0%7C0%7C637622857842435091%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=neToqnx5fZoTT%2Ba%2BE00A1B0iisp3Of%2BQcfAVXQVizCA%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKONP73ZHJGHHMYTGDIZQVDTYPZ5LANCNFSM5APUP3OQ&data=04%7C01%7Cdoermann%40buffalo.edu%7Cbc383af2d1e44224a1d708d94a9c6521%7C96464a8af8ed40b199e25f6b50a20250%7C0%7C0%7C637622857842435091%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=bYtwsuipJi7KnHxPt82ftcY%2Fq1qN8Q3U49GaizDiYxg%3D&reserved=0.

[robindijkhof]

Thank you so much! I just realized that there are custom filters. I'll try that next time. I'm not a great programmer anymore, but I think I can handle some regex! I also see a sync scroll now, but I don't remember updating. Do I need to update to get the latest version manually? May it be nice to have the version or version date on the plugin on the toolbar? Dave

I have no idea how updating works. I have been asking myself the same question.