Full text search for "page"
- 20101117_spd400_filesystem_yaffs2 . . . . 2 matches
||Can execute code ||Yes ||No, but newer chips can execute a small loader out of the first page(삼성의 OneNAND가 여기에 해당합.) ||
||Bit twiddling ||nearly unrestricted ||1-3 times, also known ad "partial page program restriction" ||
- 20101203_spd400_filesystem_install_guide . . . . 1 match
erase size와 page size의 얼라인이 맞아야 하기 때문에 이미지의 사이즈가 중요 합니다.
- AliasPageNames . . . . 1 match
# $Id: AliasPageNamesDefaultKo,v 1.1 2009/01/02 17:26:39 root Exp root $
# $aliaspage=$data_dir.'/text/AliasPageNames';
# InterMap에는 TwinPages가 정의되어 있는지 확인하시기 바랍니다.
DeleteThisPage,DeletePage,DeleteMe
- CalendarMacro . . . . 2 matches
'''YEAR-MONTH subpage is created'''
{{{[[Calendar("Blog",blog)]]}}} blog mode with default page
- CalendarMacro/UserPreferences . . . . 1 match
CategoryHomepage
- CategoryEmpty . . . . 1 match
A category for empty pages. See also DeleteThisPage.
- CategoryHomepage . . . . 2 matches
A category for WikiHomePage''''''s.
Note that such pages are "owned" by the respective person, and should not be edited by others, except to leave a message to that person. To do so, just append your message to the page, after four dashes like so:
- CategoryMacro . . . . 2 matches
If you click on the title of a category page, you'll get a list of pages belonging to that category
- CategorySoftwareTool . . . . 2 matches
If you click on the title of a category page, you'll get a list of pages belonging to that category
- CategoryTemplate . . . . 2 matches
If you click on the title of a category page, you'll get a list of pages belonging to that category
- DNN_index . . . . 1 match
(http://www.cs.ubc.ca/~shafaei/homepage/projects/dlgroup.php)
- DeleteThisPage . . . . 1 match
A marker for pages that should be deleted.
- FortuneCookies . . . . 1 match
* Many pages make a thick book.
- HelpIndex . . . . 1 match
The following is a list of all help pages:
[[PageList(Help.*)]]
- HelpOnActions . . . . 26 matches
Actions are tools that work on a page or the whole wiki, but unlike macros do not add ''to'' the page content when viewing a page, but work ''on'' that page content. They either produce some output based on page contents (navigational actions like searching) or implement functions that are not related to viewing a page (like deleting or renaming a page).
There is a set of system-defined actions, which includes page editing; you can extend the set of known actions by your own ones. See HelpForDevelopers for more on that.
The following actions are added to the list of user-defined extension actions at the bottom of each page or other position defend on your selected theme. This happens to any mixed-case extension, for other actions (all lower-case) see the list further down this page. Some of these action might not be available for this wiki site.
* `!UploadFile`: upload files to a page, see UploadFile for more details.
* `!DeletePage`: Delete a page, after you confirmed it; deletion means a final backup copy is created and only then the page is deleted, i.e. you can ''revive'' the page later on (as long as the backups are not physically deleted).
* `!LikePages`: list pages whose title starts or ends with the same MeatBall:WikiWord as the current page title.
The following is a list of ''internal'' actions that are used to implement the various menus and links at the top and bottom of pages, or supplement certain macros.
* `edit`: edit this page.
* `diff`: display differences between page revisions.
* `info`: show meta-data on a page.
* `show`: display a page (the default action).
* `print`: show the print-view of a page, which omits the navigational items from the display view.
* `subscribe`: subscribe to a page.
* `recall`: display an older revision of a page.
* `rename`: Rename a page, after you confirmed it.
* `titleindex`: Implements the listing of all page names as text (Self:?action=titleindex) or XML (Self:?action=titleindex&mimetype=text/xml''''''); the main use of this action is to enable MeatBall:MetaWiki.
- HelpOnConfiguration . . . . 3 matches
메뉴의 대문(FrontPage)및 로고 그림이 연결하고 있는 페이지는 config.php의 다음 변수를 설정한다.
* $frontpage='FrontPage';
* $logo_page=$frontpage;
- HelpOnLinking . . . . 6 matches
위키위키에서는 외부의 위키 혹은 위키위에 준하는 다른 사이트를 좀 더 쉽게 연결하는 문법을 제공합니다. 예를 들어, {{{http://moniwiki.kldp.org/wiki/FrontPage}}}라고 링크를 거는 대신에 {{{MoniWiki:FrontPage}}}라고 링크를 걸면 MoniWiki:FrontPage 처럼 표시가 됩니다. 이를 인터위키 연결이라고 합니다.
앞부분에서도 언급한 내용이지만, 자동으로 링크가 걸릴 경우 URL 주소 되에 공백을 넣어주거나, <http://moniwiki.kldp.org/wiki.php/FrontPage>와 같이 연결해주어야 합니다. 정리해보면
In addition to the standard schemas, there are MoinMoin-specific ones: `wiki:`, `attachment:`. "`wiki:`" indicates an InterWiki link, so `MoniWiki:FrontPage` and `wiki:MoniWiki:FrontPage` are equivalent; you will normally prefer the shorter form, the "`wiki`" scheme becomes important when you use bracketed links, since there you always need a scheme. The other three schemes are related to file attachments and are explained on HelpOnActions/AttachFile.
* [http://moniwiki.sourceforge.net/ MoniWiki Sourceforge Homepage]
* [wiki:MeatBall:InterWiki InterWiki page on MeatBall]
* [http://moniwiki.sourceforge.net/ MoniWiki Sourceforge Homepage]
* [wiki:MeatBall:InterWiki InterWiki page on MeatBall]
/!\ To get rid of confusion, {{{wiki:InterWiki/Page}}} link method is not supported by MoniWiki.
{{{wiki:MeatBall/InterWiki}}} is interpreted as {{{wiki:MeatBall:InterWiki}}} in the MoinMoin. But it confuse users with {{{wiki:WikiPage/SubPage}}} syntax.
And you can enable/disable !WikiName syntax by add `#camelcase` or `#camelcase 0` to the top of some pages. (Please see also ProcessingInstructions)
* without pagename like as {{{MoinMoin:}}} MoinMoin: {{{MoinWiki:}}} MoniWiki:
- HelpOnMacros . . . . 18 matches
Macros allow the insertion of system features into normal wiki pages; the only thing that makes those pages special is that they contain macros. If you edit pages like RecentChanges or SystemInfo, you'll see what that means.
||{{{[[TitleSearch]]}}} || search the page titles || FindPage ||
||{{{[[FullSearch]]}}} || search the page contents || FindPage ||
||{{{[[GoTo]]}}} || directly go to the page you enter || FindPage ||
||{{{[[PageList(regex)]]}}} || list of pages whose title matches the regex || HelpIndex ||
||{{{[[RecentChanges]]}}} || a list of recently edited pages || RecentChanges ||
||{{{[[TitleIndex]]}}} || an index of all page titles || TitleIndex ||
||{{{[[WordIndex]]}}} || an index of all words in page titles || WordIndex ||
||{{{[[RandomPage]]}}} || a link to a random page || [[RandomPage]] ||
||{{{[[RandomPage(#)]]}}} || links to a number of random pages || [[RandomPage(2)]] ||
||{{{[[PageCount]]}}} || current page count || [[PageCount]] pages ||
||{{{[[PageHits]]}}} || display page hits || [PageHits] ||
||{{{[[Include(HelloWorld[,heading[,level]])]]}}} || include contents of another page || [[Include(HelloWorld)]] ||
||{{{[[Comment]]}}} || display page comment || {{{[[Comment]]}}} ||
We don't show examples for all macros here, because that would make this page quite long. Here is is the replacement text for the {{{[[SystemInfo]]}}} macro:
- HelpOnNavigation . . . . 16 matches
The header on each page allows you to go to the FrontPage (home), RecentChanges (recent modifications), TitleIndex (index of all the page titles), WordIndex (index of all the words in the page titles), and HelpContents (main help page).
* [[Icon(moin-show.gif)]] refreshes the current page
* [[Icon(moin-print.gif)]] shows a printable version of the page without the header or footer
* [[Icon(moin-edit.gif)]] allows you to say something, i.e. edit the page
* [[Icon(moin-info.gif)]] shows meta information about the page, especially the full version history
* [[Icon(moin-diff.gif)]] shows changes between the current version and the previous version of the page
* [[Icon(moin-search.gif)]] shows the search page.
* [[Icon(moin-help.gif)]] shows the help page
Clicking on the Page Title link located in the header above will show every page that references this page. A sample use of this back-referencing, inverted-links feature is the categorization of pages, i.e. CategoryHomepage.
On the bottom of each page, you find the "traditional" edit and search links known from the original wiki.
- HelpOnPageCreation . . . . 17 matches
== Creating a New Page ==
To create a page, add its WikiName to an existing page and save it. After that, you can click on it on the revised page, since it automatically becomes a hyperlink.
You will then be presented with your new page, which you can edit in the normal way. After you ''first'' saved it, it will be automatically created. Pages normally[[FootNote(Deleting pages can be activated by the wiki administrator (which you'll normally do in intranet sites only).)]] cannot be deleted, so be sure to spell new WikiName''''''s correctly.
On details on how to create and link to subpages, see HelpOnEditing/SubPages.
== Creating and Using Template Pages ==
To create a template, follow the above description and create a page with a name ending in "'''Template'''"[[FootNote(If the wiki administrator changed the default settings, rules for what names are template pages might be different.)]]. This page will then be added to the list of template pages displayed when you try to show a non-existent page. For example, NonExistentHelpPage has a link to HelpTemplate that loads the content of HelpTemplate into the editor box, when you click on that link.
== Variable Substitution when Saving a Page ==
The following variables are substituted when a page is ''finally'' saved. Note that they'll appear unreplaced in the preview!
|| @''''''PAGE@ || Name of the page (useful for template pages) ||
Note that saving template or form definition pages and using preview does ''not'' expand variables. Other than that, variable expansion is very global and happens anywhere on the page, including code displays, comments, processing instructions and other "special" areas of a page you might think are excluded.
- HelpOnPageDeletion . . . . 9 matches
== How to delete pages ==
If enabled (see HelpOnConfiguration), you can delete pages with the {{{DeletePage}}} action. Note that deleting means to make a backup copy of the page, and then deleting the page file. This is almost like saving an empty page.
What this means is that you can get back at deleted pages by using the standard mechanisms. If you enter the page name into the `!GoTo` dialog form, you'll see the usual page creation stuff, but clicking on `!PageInfo` will reveal the old version history, unless the page was purged by WikiMaster out of existence inbetween.
- HelpOnProcessingInstructions . . . . 8 matches
MoinMoin processing instructions have the same semantics as in XML: they control the paths taken when processing a page. Processing instructions are lines that start with a "{{{#}}}" character followed by a keyword and optionally some arguments. Two consecutive hash marks at the start of a line are a comment that won't appear in the processed page.
* {{{#FORMAT}}} ''format-specifier'': defines the input format for this page, known formats are:
* {{{#REDIRECT}}} ''pagename'': redirect to a different page (see MeatBall:PageRedirect'''''')
All PIs must appear at the very start of a page. An exception are comment PIs, those may appear within a wiki page (but obviously not in pages using other formats).
- HelpOnSmileys . . . . 1 match
make EditTextForm page like following
- HelpOnSpellCheck . . . . 2 matches
* the page LocalSpellingWords
If the "dbhash" module is available with your Python installation, the files in "dict" are read only ''once'' and stored in a hash table. This speeds up the spell checking process because then the number of words in the ''checked page'' determines the time needed for the checking, ''not'' the number of words in the dictionary (with 250000 words, some hundred milliseconds instead of several seconds).
- HelpOnUpdating . . . . 3 matches
* somewhat dangerous macros that won't be activated by default, because they're not advisable for public wikis. You need to explicitely activate those by adding an {{{allowed_actions}}} list to the config. Currently, protected actions {{{DeletePage}}} are always needs 'admin password'.
System pages or WikiSeed''''''s :: When upgrading to a new version, copy at least the help pages ("Help*") to
your existing directory. Then check whether you miss any new system pages.
- HelpOnUserPreferences . . . . 7 matches
* '''[[GetText(Subscribed wiki pages (one regex per line))]]''': Enter '''`.*`''' to receive an email when any page in this Wiki changes (''not recommended'' for busy wikis), or enter the names of any individual pages, one per line. If you are familiar with '''regular expressions''', you may enter a regex expression to match the pages names of interest (.* matches all page names). With the '''[[GetText(Show icon toolbar)]]''' option checked, subscription to individual pages is made easy by clicking the envelope icon when viewing a page of interest.
- HomepageTemplate . . . . 1 match
CategoryHomepage
- InterWiki . . . . 1 match
See the MeatBall:InterWiki page on wiki:MeatBall:MeatballWiki for further details.
- Linux_device_Dynamic_DMA_mapping . . . . 14 matches
''Most of the 64bit platforms have special hardware that translates bus addresses (DMA addresses) to physical addresses similarly to how page''
''This is needed so that e.g. PCI devices can access with a Single Address Cycle (32bit DMA address) any page in the 64bit physical address space.''
''works (the DMA address translation tables were simply filled on bootup to map each bus address to the physical page __pa(bus_to_virt())).''
''If you acquired your memory via the page allocator (i.e. __get_free_page*()) or the generic memory allocators (i.e. kmalloc() or kmem_cache_alloc()) then you may DMA to/from that memory using the addresses returned from those routines.''
Page allocator나 Generic memory allocator를 통해서 메모리를 할당 받아서 DMA에 사용한다.
''This means specifically that you may not use the memory/addresses returned from vmalloc() for DMA. It is possible to DMA to the _underlying_ memory mapped into a vmalloc() area, but this requires walking page tables to get the physical addresses, and then translating each of those pages back to a kernel address using
''To allocate and map large (PAGE_SIZE or so) consistent DMA regions,''
''This routine will allocate RAM for that region, so it acts similarly to__get_free_pages (but takes size instead of a page order). If your driver needs regions sized smaller than a page, you may prefer using the pci_pool interface, described below.''
''The cpu return address and the DMA bus master address are both guaranteed to be aligned to the smallest PAGE_SIZE order which is greater than or equal to the requested size. This invariant exists (for example) to guarantee that if you allocate a chunk which is smaller than or equal to 64 kilobytes, the extent of the buffer you receive will not cross a 64K boundary.''
''If your driver needs lots of smaller memory regions, you can write custom code to subdivide pages returned by pci_alloc_consistent, or you can use the pci_pool API to do that. A pci_pool is like a kmem_cache, but it uses pci_alloc_consistent not __get_free_pages. Also, it understands common hardware constraints for alignment, like queue heads needing to be aligned on N byte boundaries.''
''Another advantage of specifying this value precisely (outside of potential platform-specific optimizations of such) is for debugging. Some platforms actually have a write permission boolean which DMA mappings can be marked with, much like page protections in a user program can have. Such platforms can and do report errors in the kernel logs when the PCI controller hardware detects violation of the permission setting.''
''The implementation is free to merge several consecutive sglist entries into one (e.g. if DMA mapping is done with PAGE_SIZE granularity, any consecutive sglist entries can be merged into one provided the first one ends and the second one starts on a page boundary - in fact this is a huge advantage for cards which either cannot do scatter-gather or have very limited number of scatter-gather entries) and returns the actual number of sg entries it mapped them to.''
- Linux_device_module_basic . . . . 2 matches
ssize_t (*sendpage) (struct file *, struct page *, int, size_t, loff_t *, int);
- LocalKeywords . . . . 45 matches
pages WymSkPhN
pages WymSkPhN
pages WymSkPhN
page WymSkPhN
page WymSkPhN
page WymSkPhN
pages WymSkPhN
page WymSkPhN
pages WymSkPhN
page WymSkPhN
pages WymSkPhN
page WymSkPhN
pages WymSkPhN
page WymSkPhN
pages WymSkPhN
page WymSkPhN
pages WymSkPhN
page WymSkPhN
pages WymSkPhN
page WymSkPhN
- MoniWiki/HotKeys . . . . 1 match
||L||action=LikePages || ||
||A||action=randompage || ||
||F 또는 H||action=home ||FrontPage ||
||Q, S, R(Safari only)[[BR]]또는 F3(Firefox only)|| ||[[Icon(search)]] FindPage ||
- MoniWikiACL . . . . 19 matches
* 일부 POST액션은 관리자 비밀번호로 제한을 걸어둘 수 있는 액션은 protect 가능한 액션입니다. protect 액션은 ''제한된 allow''이며, 일부 POST액션만 지원합니다. 예) do_post_savepage()는 post 액션이며, 일반 do_goto()같은 액션과는 달리 관리자 비밀번호로 액션을 제한을 할 수 있습니다.
FoobarPage @ALL allow *
FoobarPage babo deny edit,diff,info
HelpOn.* @ALL deny edit,savepage
* @ALL allow read,userform,rss_rc,aclinfo,fortune,deletepage,fixmoin,ticket // 여러 줄로 나눠쓰기 가능
# some pages are allowed to edit
* @ALL protect deletefile,deletepage,rename,rcspurge,rcs,chmod,backup,restore
// 모든 페이지(*)에 대해 모든 사용자의(@ALL) detetefile,deltetepage 등등의 protect 가능한 액션을 protect
* @ALL allow read,userform,rss_rc,aclinfo,fortune,deletepage,fixmoin,ticket
# some pages have restrict permission
모든 페이지에 대해서 읽기만 가능하게, ProtectedPage에 대해서는 읽기도 거부
ProtectedPage @ALL deny read
ProtectedPage는 {{{deny *}}} + {{{allow read}}} + {{{deny read}}} = {{{deny *}}}이 된다.
ProtectedPage @ALL deny *
ProtectedPage는 {{{deny *}}} + {{{allow read}}} + {{{deny *}}}이 된다: explicit하게 허락된 read가 허용된다.
마지막 줄 {{{ProtectedPage @ALL deny *}}}는 무시되게 되는 것이다.
* @ALL allow read,ticket,info,diff,titleindex,bookmark,pagelist
ProtectedPage @All deny read,ticket,info,diff,titleindex,bookmark,pagelist
* ProtectedPage는 edit,savepage를 제외하고 모두 불허
* @ALL allow show,ticket,titleindex,bookmark,pagelist
- MoniWikiOptions . . . . 4 matches
`'''$frontpage="페이지이름";'''`
* 대문을 지정한다. 기본값은 FrontPage.
`'''$logo_page="페이지이름";'''`
* 로고를 클릭할 때 가는 페이지를 정한다. 기본값은 $frontpage.
`'''$menu=array('MoniWiki'=>1,'FindPage'=>4,'TitleIndex'=>3,'BlogChanges'=>'','RecentChanges'=>2,'http://kldp.org KLDP'=>9);'''`
* 페이지 카운터의 사용 여부를 결정한다 (See PageHitsMacro)
`'''$use_twinpages'''`
- RecentChangesMacro . . . . 1 match
이름이야 엿장수 맘이지만, 전 .rcTable, .icon, .page, .timestamp로 했습니다.
- WikiSlide . . . . 49 matches
* a technology for collaborative creation of internet and intranet pages
* '''Interlinked''' - Links between pages are easy to make
* Email address for subscribing to page change emails and retrieving a lost login/password
* Structure of pages
* "Recently visited pages" (see UserPreferences)
* Title search and full text search at bottom of page
* WikiSandBox: Sandbox page to play around and experiment with
* FindPage: Searching the Wiki by various methods
* TitleIndex: A list of all pages in the Wiki
* WordIndex: A list of all words in page titles (i.e. a list of keywords/concepts in the Wiki)
To edit a page, just click on [[Icon(edit)]] or on the link "`EditText`" at the end of the page. A form will appear enabling you to change text and save it again. A backup copy of the previous page's content is made each time.
You can check the appearance of the page without saving it by using the preview function - ''without'' creating an entry on RecentChanges; additionally there will be an intermediate save of the page content, if you have created a homepage ([[Icon(home)]] is visible).
<!> After editing pages, please leave the edit form by "`Save Changes`" since otherwise your edits will be lost!
(!) In UserPreferences, you can set up the editor to open when you double click a page.
(!) You can subscribe to pages to get a mail on every change of that page. Just click on the envelope [[Icon(subscribe)]] at top right of the page.
|| {{{PageReference WikiSandBox}}} || PageReference WikiSandBox ||
* Macros allow dynamic (computed) content to be inserted into pages.
* `PageList` - generates lists of pages with titles matching a pattern
== Creating new Pages ==
New pages are created by simply adding a new WikiName to an existing page and clicking on it after saving the existing page.
- WikiWikiWeb . . . . 1 match
The [wiki:Wiki:FrontPage first ever wiki site] was founded in 1994 as an automated supplement to the Wiki:PortlandPatternRepository. The site was immediately popular within the pattern community, largely due to the newness of the internet and a good slate of Wiki:InvitedAuthors. The site was, and remains, dedicated to Wiki:PeopleProjectsAndPatterns.
Wiki:WardCunnigham created the site and the WikiWikiWeb machinery that operates it. He chose wiki-wiki as an alliterative substitute for quick and thereby avoided naming this stuff quick-web. An early page, Wiki:WikiWikiHyperCard, traces wiki ideas back to a Wiki:HyperCard stack he wrote in the late 80's.
* http://www.c2.com/cgi/wiki or wiki:Wiki/FrontPage
- WkPark/UserPreferences . . . . 2 matches
If you click on the title of a category page, you'll get a list of pages belonging to that category
- config.php . . . . 1 match
FrontPage Anonymous allow read
$use_subindex=1; # use subpage indices
- cv_report3 . . . . 1 match
com_board_basic=read_form&com_board_idx=710&topmenu=5&left=5&&com_board_search_code=&com_board_search_value1=&com_board_search_value2=&com_board_page=1&> (4 Dec 2017)] 를 갖는다.
- embaded_nand_flash_memory . . . . 4 matches
'''Page'''
- 하나의 Block은 보통 512Byte ~ 8KByte 크기를 가지는 다수의 page들로 구성됨.
- Page는 NAND flash의 읽기 및 쓰기의 기본 단위,
- Page마다 따라오는 수~수백 byte 정도 크기의 extra 데이터 영역으로 16의 배수 byte인 경우가 많다. spare 영역이라고도 불린다.
1. Bad Block Marking : 특정 블록이 Bad block일 경우 한 Block 안의 첫 page 혹은 마지막 page의 OOB에 이를 표시함.
예를 들어 최근에 출시되는 삼성 NAND는 공장 출하시부토 존재하는 bad block을 표시하기 위해서 bad block의 마지막 page의 첫 byte를 Non-FF value로 표시함.
- factorized_vae_and_annealed_vae . . . . 1 match
본 논문에서는 N명의 청중이 T시간 동안 영화를 보면서 짓는 표정 변화 측정했다. 표정은 \(D = 136\) Demensional vector로 표현했다. 이렇게 관촬한 데이터를 \(N \times T \times D\) tensor \(X\)라 하자. 이를 Tensor Factorization 알고리즘인 PARAFAC decomposition[* https://www.cs.cmu.edu/~pmuthuku/mlsp_page/lectures/Parafac.pdf]을 사용해 \(K\) rank(latent facrots)를 갖는 3개의 matrix로 분활했다. \(U \in \mathbb{R}^{N \times K}\), \(V \in \mathbb{R}^{T \times K}\) 그리고 \(F \in \mathbb{R}^{D \times K}\)
- filesystem_yaffs_jffs2 . . . . 10 matches
int imglen, pagelen;
/* Check, if image is pagealigned */
pagelen = nand->writesize + nand->oobsize;
if ((off % nand->erasesize) != 0 || (imglen % pagelen) != 0) {
printf ("Input image is not page aligned off = %d erasesize = %d imglen = %d pagelen = %d\n", off, nand->erasesize, imglen, pagelen);
if ( ((imglen / pagelen) * nand->writesize) > (nand->size - off)) {
/* Write out the Page data */
imgptr += pagelen;
imglen -= pagelen;
- game_pvpgn_install . . . . 1 match
http://pvpgn.berlios.de/index.php?page=files
- index_2010 . . . . 1 match
#title Cats eye Front Page
[http://forum.falinux.com/zbxe/?mid=hardware&page=3 NAND에 대한 설명]
- linux_Voyager_install . . . . 2 matches
http://manpages.ubuntu.com/manpages/hardy/man1/bchunk.1.html
- linux_gitweb_install_guide . . . . 2 matches
# target of the home link on top of all pages
# html text to include at home page
- linux_init_setup . . . . 1 match
# See the manual page of ypbind for the syntax of this file.
- neovim . . . . 1 match
echom 'new wiki page has created'
- osx_utility . . . . 1 match
* mpc - http://www.multiprecision.org/index.php?prog=mpc&page=download
- raspberrypi4 . . . . 1 match
https://sysops.tv/?page_id=28
- test . . . . 1 match
http://itempage.auction.co.kr/DetailView.aspx?ItemNo=A532200175
- vae_gan . . . . 1 match
Variational Inference를 활용한 연구중 가장 최근의 연구라면 VAE를 꼽을 수 있다. VAE는 2013년 Kingma et al.[* Diederik P. Kingma and Max Welling. '''Auto-encoding variational bayes'''.CoRR, abs/1312.6114, 2013.]과 Rezende et al.[* Danilo Jimenez Rezende, Shakir Mohamed, and Daan Wierstra. '''Stochastic backpropagation and approximate inference in deep generative models'''. In Proceedings of the 31st International Conference on Machine Learning - Volume 32, ICML’14, pages II–1278–II–1286.JMLR.org, 2014.]에 의해 정의 되었습니다. Variational Autoencoder를 이해하기 위해서는 간단한 Autoencoder의 구조부터 이해해야 합니다.
- wskim_atrix_customrom . . . . 1 match
[http://www.startpda.kr/zbxe/index.php?page=2&document_srl=1669766 PDA Start 강좌 글]
Found 54 matching pages out of 775 total pages
You can also click here to search title.
Whansun`s Deep learning Wiki