Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Ready to release v0.1.0
See original GitHub issueSummary
기본적으로 전체적인 틀은 잡혀있는 사항 v0.1.0을 release하기에 앞서 다음의 내용에 대해서 논의
serialize_corpora.py와train_tokenizer.py가 지원하는model_type에 이격이 존재serialie_corpora.py:roberta,gpt2,alberttrain_tokenizer.py:bert-uncased,bert-cased,gpt2,roberta,albert,electra
README.md
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Release v0.1.0 · GitHub
Release v0.1.0. Product. Actions. Automate any workflow · Packages. Host and manage packages · Security. Find and fix vulnerabilities.
Read more >AsyncAPI Initiative on Twitter: "Release v0.1.0 for asyncapi/bundler ...
Release v0.1.0 for asyncapi/bundler is out in the wild Thank you for ... 0.1.0 (2022-02-07) Features get bundler ready to release (#17) (1ee2313)....
Read more >Neatline for Omeka S: Development Release v0.1.0
We're happy to share a development release of Neatline for Omeka S. The version for this release is 0.1.0, so it's not yet...
Read more >Release - Mun v0.1.0 - Mun Programming Language
We are proud to present Mun v0.1.0 - our first milestone release. As a language, Mun is still far from production-ready, but this...
Read more >Just Want A Go Release Tool? | by nwillc - Level Up Coding
In Go, the releases mechanism is part of the module system. ... git commit -am 'Ready for release v0.1.0' # Now tag it...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
NSP가 아닌 SOP를 사용할 예정이라면 BertProcessor를 AlbertProcessor를 상속받은 형태로만 작성하면 될 것 같고, 사용여부를 옵션으로 주는 것이 아니라 SOP를 무조건 사용하도록 하는 것이 맞을 것 같습니다. 이 경우 Electra는 원하면 구현하고 (아마도 근데 Electra의 경우 Pretrained BERT가 필요해서 제외하는 게 낫지 않을까 싶습니다만…) 아니면 이번 릴리즈에서는 제외해도 좋을 것 같습니다 😃
어느 정도 해결되어 close합니다.