Papers › StoryDALL-E: Adapting Pretrained Text-to-Image Transformers for Story Continuation

StoryDALL-E: Adapting Pretrained Text-to-Image Transformers for Story Continuation

13 Sep 2022arXiv:2209.06192archive 2025-07-28

Adyasha Maharana, Darryl Hannan, Mohit Bansal

Recent advances in text-to-image synthesis have led to large pretrained transformers with excellent capabilities to generate visualizations from a given text. However, these models are ill-suited for specialized tasks like story visualization, which requires an agent to produce a sequence of images given a corresponding sequence of captions, forming a narrative. Moreover, we find that the story visualization task fails to accommodate generalization to unseen plots and characters in new narratives. Hence, we first propose the task of story continuation, where the generated visual story is conditioned on a source image, allowing for better generalization to narratives with new characters. Then, we enhance or 'retro-fit' the pretrained text-to-image synthesis models with task-specific modules for (a) sequential image generation and (b) copying relevant elements from an initial frame. Then, we explore full-model finetuning, as well as prompt-based tuning for parameter-efficient adaptation, of the pre-trained model. We evaluate our approach StoryDALL-E on two existing datasets, PororoSV and FlintstonesSV, and introduce a new dataset DiDeMoSV collected from a video-captioning dataset. We also develop a model StoryGANc based on Generative Adversarial Networks (GAN) for story continuation, and compare it with the StoryDALL-E model to demonstrate the advantages of our approach. We show that our retro-fitting approach outperforms GAN-based models for story continuation and facilitates copying of visual elements from the source image, thereby improving continuity in the generated visual story. Finally, our analysis suggests that pretrained transformers struggle to comprehend narratives containing several characters. Overall, our work demonstrates that pretrained text-to-image synthesis models can be adapted for complex and low-resource tasks like story continuation.

PaperPDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 3 code samples harvested from 1 repository linked to this paper: 2 ran (of which 2 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified; every one of the 2 samples that ran constructed an object rather than computing a result. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 3 samples from 1 repository, 2 ran (2 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

adymaharana/storydalle officialmentioned in papermentioned on GitHubpytorchSyntology: 3 samples, 2 ran (0 instrument-failed) · 1 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

3 samples harvested: 2 ran (of which 2 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified; every one of the 2 samples that ran constructed an object rather than computing a result. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran
1unverified

Licence: 0 of the 3 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from adymaharana/storydalle. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. For 2 samples that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

adymaharana/storydalle official repository 3 samples, 2 ran (0 instrument-failed) · 1 unverified
Block in 252 papers
census: 5 implementations from 5 papers, 3 distinct outputs across 2 buckets, one shared input per bucket
story-dalle/dalle/models/stage2/transformer.py ran MIT (permissive) · 5f34dd7c6d84070b · report fixture: returned Block · level recorded 2026-09-22
MultiHeadSelfAttention in 17 papers story-dalle/dalle/models/stage2/transformer.py ran MIT (permissive) · c354cf95a9627777 · report fixture: returned MultiHeadSelfAttention · level recorded 2026-09-22
Transformer1d story-dalle/dalle/models/stage2/transformer.py unverified MIT (permissive) · b446857df78ea96c · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for StoryDALL-E (graph method: StoryDALL-E). 4 bricks; individually on a fixture: 3 ran (of which 3 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified; every one of the 3 samples that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.

  1. Transformer1d entry · level 0 · unverified · b446857df78ea96c
  2. Block helper · level 1 · ran · 5f34dd7c6d84070b
  3. GELU helper · level 1 · ran · 0b3c58ba91896ec0
  4. MultiHeadSelfAttention helper · level 1 · ran · c354cf95a9627777

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2209.06192") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Image GenerationStory ContinuationStory VisualizationVideo Captioning

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Story Continuation FlintstonesSV StoryDALL-E Char-F1 74.28 #3 of 6 Archive leaderboard report
Story Continuation FlintstonesSV StoryDALL-E F-Acc 52.35 #3 of 6 Archive leaderboard report
Story Continuation FlintstonesSV StoryDALL-E FID 28.37 #3 of 6 Archive leaderboard report
Story Continuation FlintstonesSV StoryDALL-E (Story Embeddings) Char-F1 72.18 #4 of 6 Archive leaderboard report
Story Continuation FlintstonesSV StoryDALL-E (Story Embeddings) F-Acc 53.28 #4 of 6 Archive leaderboard report
Story Continuation FlintstonesSV StoryDALL-E (Story Embeddings) FID 29.21 #4 of 6 Archive leaderboard report
Story Continuation FlintstonesSV StoryDALL-E (Cross-Attention) Char-F1 73.94 #5 of 6 Archive leaderboard report
Story Continuation FlintstonesSV StoryDALL-E (Cross-Attention) F-Acc 52.72 #5 of 6 Archive leaderboard report
Story Continuation FlintstonesSV StoryDALL-E (Cross-Attention) FID 35.04 #5 of 6 Archive leaderboard report
Story Continuation FlintstonesSV StoryDALL-E (Story Embeddings + Cross-Attention) Char-F1 72.44 #6 of 6 Archive leaderboard report
Story Continuation FlintstonesSV StoryDALL-E (Story Embeddings + Cross-Attention) F-Acc 51.32 #6 of 6 Archive leaderboard report
Story Continuation FlintstonesSV StoryDALL-E (Story Embeddings + Cross-Attention) FID 36.28 #6 of 6 Archive leaderboard report
Story Continuation PororoSV StoryDALL-E Char-F1 40.28 #3 of 6 Archive leaderboard report
Story Continuation PororoSV StoryDALL-E F-Acc 20.94 #3 of 6 Archive leaderboard report
Story Continuation PororoSV StoryDALL-E FID 21.64 #3 of 6 Archive leaderboard report
Story Continuation PororoSV StoryDALL-E (Cross-Attention) Char-F1 40.25 #4 of 6 Archive leaderboard report
Story Continuation PororoSV StoryDALL-E (Cross-Attention) F-Acc 18.16 #4 of 6 Archive leaderboard report
Story Continuation PororoSV StoryDALL-E (Cross-Attention) FID 23.27 #4 of 6 Archive leaderboard report
Story Continuation PororoSV StoryDALL-E (Story Embeddings) Char-F1 39.32 #5 of 6 Archive leaderboard report
Story Continuation PororoSV StoryDALL-E (Story Embeddings) F-Acc 34.65 #5 of 6 Archive leaderboard report
Story Continuation PororoSV StoryDALL-E (Story Embeddings) FID 30.45 #5 of 6 Archive leaderboard report
Story Continuation PororoSV StoryDALL-E (Story Embeddings + Cross-Attention) Char-F1 35.29 #6 of 6 Archive leaderboard report
Story Continuation PororoSV StoryDALL-E (Story Embeddings + Cross-Attention) F-Acc 16.73 #6 of 6 Archive leaderboard report
Story Continuation PororoSV StoryDALL-E (Story Embeddings + Cross-Attention) FID 31.68 #6 of 6 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections